I'm using the websockets
library to create a websocket server in Python 3.4. Here's a simple echo server:
import asyncio import websockets @asyncio.coroutine def connection_handler(websocket, path): while True: msg = yield from websocket.recv() if msg is None: # connection lost break yield from websocket.send(msg) start_server = websockets.serve(connection_handler, 'localhost', 8000) asyncio.get_event_loop().run_until_complete(start_server) asyncio.get_event_loop().run_forever()
Let's say we – additionally – wanted to send a message to the client whenever some event happens. For simplicity, let's send a message periodically every 60 seconds. How would we do that? I mean, because connection_handler
is constantly waiting for incoming messages, the server can only take action after it has received a message from the client, right? What am I missing here?
Maybe this scenario requires a framework based on events/callbacks rather than one based on coroutines? Tornado?
asyncio was first introduced in Python 3.4 as an additional way to handle these highly concurrent workloads outside of multithreading and multiprocessing.
gather() method - It runs awaitable objects (objects which have await keyword) concurrently.
It should be used as a main entry point for asyncio programs, and should ideally only be called once. New in version 3.7.
In asyncio's model of concurrency we have only one thread executing Python at any given time.
TL;DR Use asyncio.ensure_future()
to run several coroutines concurrently.
Maybe this scenario requires a framework based on events/callbacks rather than one based on coroutines? Tornado?
No, you don't need any other framework for this. The whole idea the asynchronous application vs synchronous is that it doesn't block, while waiting for result. It doesn't matter how it is implemented, using coroutines or callbacks.
I mean, because connection_handler is constantly waiting for incoming messages, the server can only take action after it has received a message from the client, right? What am I missing here?
In synchronous application you will write something like msg = websocket.recv()
, which would block whole application until you receive message (as you described). But in the asynchronous application it's completely different.
When you do msg = yield from websocket.recv()
you say something like: suspend execution of connection_handler()
until websocket.recv()
will produce something. Using yield from
inside coroutine returns control back to the event loop, so some other code can be executed, while we're waiting for result of websocket.recv()
. Please, refer to documentation to better understand how coroutines work.
Let's say we – additionally – wanted to send a message to the client whenever some event happens. For simplicity, let's send a message periodically every 60 seconds. How would we do that?
You can use asyncio.async()
to run as many coroutines as you want, before executing blocking call for starting event loop.
import asyncio import websockets # here we'll store all active connections to use for sending periodic messages connections = [] @asyncio.coroutine def connection_handler(connection, path): connections.append(connection) # add connection to pool while True: msg = yield from connection.recv() if msg is None: # connection lost connections.remove(connection) # remove connection from pool, when client disconnects break else: print('< {}'.format(msg)) yield from connection.send(msg) print('> {}'.format(msg)) @asyncio.coroutine def send_periodically(): while True: yield from asyncio.sleep(5) # switch to other code and continue execution in 5 seconds for connection in connections: print('> Periodic event happened.') yield from connection.send('Periodic event happened.') # send message to each connected client start_server = websockets.serve(connection_handler, 'localhost', 8000) asyncio.get_event_loop().run_until_complete(start_server) asyncio.async(send_periodically()) # before blocking call we schedule our coroutine for sending periodic messages asyncio.get_event_loop().run_forever()
Here is an example client implementation. It asks you to enter name, receives it back from the echo server, waits for two more messages from server (which are our periodic messages) and closes connection.
import asyncio import websockets @asyncio.coroutine def hello(): connection = yield from websockets.connect('ws://localhost:8000/') name = input("What's your name? ") yield from connection.send(name) print("> {}".format(name)) for _ in range(3): msg = yield from connection.recv() print("< {}".format(msg)) yield from connection.close() asyncio.get_event_loop().run_until_complete(hello())
Important points:
asyncio.async()
was renamed to asyncio.ensure_future()
.If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With