websockets
websockets copied to clipboard
Library for building WebSocket servers and clients in Python
It should be as simple as:: ``` @property def connections(self): return self.handlers.keys() ```
[414 URI Too Long](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/414) [431 Request Header Fields Too Large](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/431)
Essentially, it should behave like the asyncio server. It could also gain the connections attribute.
The library includes a `broadcast` utility, with detailed documentation and motivation [here](https://websockets.readthedocs.io/en/stable/topics/broadcast.html). However, today that utility only works with the asyncio API of WebSockets. That leaves users of the sync...
Whenever the opening handshake ends with a code other than 101, an error is logged. While this behavior was already present in the legacy implementation (I believe), it's less than...
All implementations store incoming messages to a queue; then the application reads from this queue. In the legacy asyncio, UTF-8 decoding happens in `WebSocketCommonProtocol.read_message`, before storing messages in the queue....
When reading a fragmented message, `Protocol.parse` decrements `max_size` as fragments are read. This can cause a confusing error in `Frame.parse`: `ConnectionClosedError: sent 1009 (message too big) over size limit (1048576...
Bumps [pypa/cibuildwheel](https://github.com/pypa/cibuildwheel) from 2.20.0 to 2.21.3. Release notes Sourced from pypa/cibuildwheel's releases. v2.21.3 🛠 Update CPython 3.13 to 3.13.0 final release (#2032) 📚 Docs updates and tidy ups (#2035) v2.21.2...
Seems like new asyncio server process_request can't consume bytes, it's produce extra work.