-
-
Notifications
You must be signed in to change notification settings - Fork 34.1k
gh-79012: Add asyncio chat server HOWTO #144604
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
kovan
wants to merge
2
commits into
python:main
Choose a base branch
from
kovan:gh-79012-asyncio-chat-server
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+212
−0
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,207 @@ | ||
| .. _asyncio-chat-server-howto: | ||
|
|
||
| *********************************************** | ||
| Building a TCP chat server with :mod:`!asyncio` | ||
| *********************************************** | ||
|
|
||
| This guide walks you through building a TCP chat server where multiple users | ||
| can connect and exchange messages in real time. Along the way, you will learn | ||
| how to use :ref:`asyncio streams <asyncio-streams>` for network programming. | ||
|
|
||
| The guide assumes basic Python knowledge --- functions, classes, and context | ||
| managers --- and a general understanding of async/await. | ||
|
|
||
| .. seealso:: | ||
|
|
||
| :ref:`a-conceptual-overview-of-asyncio` | ||
| An introduction to the fundamentals of asyncio. | ||
|
|
||
| :mod:`asyncio` reference documentation | ||
| The complete API reference. | ||
|
|
||
|
|
||
| .. _asyncio-chat-server-echo: | ||
|
|
||
| Starting with an echo server | ||
| ============================ | ||
|
|
||
| Before building the chat server, let's start with something simpler: an echo | ||
| server that sends back whatever a client sends. | ||
|
|
||
| The core of any asyncio network server is :func:`asyncio.start_server`. You | ||
| give it a callback function, a host, and a port. When a client connects, | ||
| asyncio calls your callback with two arguments: a | ||
| :class:`~asyncio.StreamReader` for receiving data and a | ||
| :class:`~asyncio.StreamWriter` for sending data back. Each connection runs | ||
| as its own coroutine, so multiple clients are handled concurrently. | ||
|
|
||
| Here is a complete echo server:: | ||
|
|
||
| import asyncio | ||
|
|
||
| async def handle_client(reader, writer): | ||
| addr = writer.get_extra_info('peername') | ||
| print(f'New connection from {addr}') | ||
|
|
||
| while True: | ||
| data = await reader.readline() | ||
| if not data: | ||
| break | ||
| writer.write(data) | ||
| await writer.drain() | ||
|
|
||
| print(f'Connection from {addr} closed') | ||
| writer.close() | ||
| await writer.wait_closed() | ||
|
|
||
| async def main(): | ||
| server = await asyncio.start_server( | ||
| handle_client, '127.0.0.1', 8888) | ||
| addr = server.sockets[0].getsockname() | ||
| print(f'Serving on {addr}') | ||
|
|
||
| async with server: | ||
| await server.serve_forever() | ||
|
|
||
| asyncio.run(main()) | ||
|
|
||
| The :meth:`~asyncio.StreamWriter.write` method buffers data without sending | ||
| it immediately. Awaiting :meth:`~asyncio.StreamWriter.drain` flushes the | ||
| buffer and applies back-pressure if the client is slow to read. Similarly, | ||
| :meth:`~asyncio.StreamWriter.close` initiates shutdown, and awaiting | ||
| :meth:`~asyncio.StreamWriter.wait_closed` waits until the connection is | ||
| fully closed. | ||
|
|
||
| To test, run the server in one terminal and connect from another using ``nc`` | ||
| (or ``telnet``): | ||
|
|
||
| .. code-block:: none | ||
|
|
||
| $ nc 127.0.0.1 8888 | ||
|
|
||
|
|
||
| .. _asyncio-chat-server-building: | ||
|
|
||
| Building the chat server | ||
| ======================== | ||
|
|
||
| The chat server extends the echo server with two additions: tracking connected | ||
| clients and broadcasting messages to everyone. | ||
|
|
||
| We store each client's name and :class:`~asyncio.StreamWriter` in a dictionary. | ||
| When a message arrives, we broadcast it to all other connected clients. | ||
| :class:`asyncio.TaskGroup` sends to all recipients concurrently, and | ||
| :func:`contextlib.suppress` silently handles any :exc:`ConnectionError` from | ||
| clients that have already disconnected. | ||
|
|
||
| :: | ||
|
|
||
| import asyncio | ||
| import contextlib | ||
|
|
||
| connected_clients: dict[str, asyncio.StreamWriter] = {} | ||
|
|
||
| async def broadcast(message, *, sender=None): | ||
| """Send a message to all connected clients except the sender.""" | ||
| async def send(writer): | ||
| with contextlib.suppress(ConnectionError): | ||
| writer.write(message.encode()) | ||
| await writer.drain() | ||
|
|
||
| async with asyncio.TaskGroup() as tg: | ||
| # Iterate over a copy: clients may leave during the broadcast. | ||
| for name, writer in list(connected_clients.items()): | ||
| if name != sender: | ||
| tg.create_task(send(writer)) | ||
|
|
||
| async def handle_client(reader, writer): | ||
| addr = writer.get_extra_info('peername') | ||
|
|
||
| writer.write(b'Enter your name: ') | ||
| await writer.drain() | ||
| data = await reader.readline() | ||
| if not data: | ||
| writer.close() | ||
| await writer.wait_closed() | ||
| return | ||
|
|
||
| name = data.decode().strip() | ||
| connected_clients[name] = writer | ||
| print(f'{name} ({addr}) has joined') | ||
| await broadcast(f'*** {name} has joined the chat ***\n', sender=name) | ||
|
|
||
| try: | ||
| while True: | ||
| data = await reader.readline() | ||
| if not data: | ||
| break | ||
| message = data.decode().strip() | ||
| if message: | ||
| print(f'{name}: {message}') | ||
| await broadcast(f'{name}: {message}\n', sender=name) | ||
| except ConnectionError: | ||
| pass | ||
| finally: | ||
| # Ensure cleanup even if the client disconnects unexpectedly. | ||
| del connected_clients[name] | ||
| print(f'{name} ({addr}) has left') | ||
| await broadcast(f'*** {name} has left the chat ***\n') | ||
| writer.close() | ||
| await writer.wait_closed() | ||
|
|
||
| async def main(): | ||
| server = await asyncio.start_server( | ||
| handle_client, '127.0.0.1', 8888) | ||
| addr = server.sockets[0].getsockname() | ||
| print(f'Chat server running on {addr}') | ||
|
|
||
| async with server: | ||
| await server.serve_forever() | ||
|
|
||
| asyncio.run(main()) | ||
|
|
||
| To test, start the server and connect from two or more terminals using ``nc`` | ||
| (or ``telnet``): | ||
|
|
||
| .. code-block:: none | ||
|
|
||
| $ nc 127.0.0.1 8888 | ||
| Enter your name: Alice | ||
| *** Bob has joined the chat *** | ||
| Bob: Hi Alice! | ||
| Hello Bob! | ||
|
|
||
| Each message you type is broadcast to all other connected users. | ||
|
|
||
|
|
||
| .. _asyncio-chat-server-timeout: | ||
|
|
||
| Adding an idle timeout | ||
| ====================== | ||
|
|
||
| To disconnect clients who have been idle for too long, wrap the read call in | ||
| :func:`asyncio.timeout`. This async context manager takes a duration in | ||
| seconds. If the enclosed ``await`` does not complete within that time, the | ||
| operation is cancelled and :exc:`TimeoutError` is raised. This frees server | ||
| resources when clients connect but stop sending data. | ||
|
|
||
| Replace the message loop in ``handle_client`` with:: | ||
|
|
||
| try: | ||
| while True: | ||
| try: | ||
| async with asyncio.timeout(300): # 5-minute timeout | ||
| data = await reader.readline() | ||
| except TimeoutError: | ||
| writer.write(b'Disconnected: idle timeout.\n') | ||
| await writer.drain() | ||
| break | ||
| if not data: | ||
| break | ||
| message = data.decode().strip() | ||
| if message: | ||
| await broadcast(f'{name}: {message}\n', sender=name) | ||
| except ConnectionError: | ||
| pass | ||
| finally: | ||
| # ... (cleanup as before) ... | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there are too many new concepts being introduced all at once. Let's focus on getting the user familiar with
asyncio.start_server, and then we can start adding behavior to callbacks.