Summary

Fixes the documentation in "Memory and Buffers" topic page which incorrectly stated thatmax_queue doesn't exist in the threading implementation.

Issue

The documentation stated:

In the :mod:threading implementation, there is no queue of incoming messages. Themax_queue argument doesn't exist. The connection keeps at most one message in memory at a time.

However, the threading (sync) implementationdoes have themax_queue argument and it works the same way as in the new asyncio implementation.

Changes

Updateddocs/topics/memory.rst to correctly document that:

• Themax_queue argument exists in the threading implementation
• It has the same semantics as the new asyncio implementation
• It is the high-water mark of a queue of incoming frames
• It defaults to 16 frames (same as asyncio)
• It provides backpressure control when the queue grows above the high-water mark

Context

As noted by@aaugustin in the issue,max_queue wasn't in the initial version of the threading implementation but was added later as a performance optimization. The documentation was never updated to reflect this change.

Closes#1544

Fixes#1664

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn moreCopilot coding agent tips in the docs.