There is a problem when a large (>345 kB) message is being written to a websocket. The connection will actually time out, unless this while is in place. Unfortunately, this pretty much busy-waits. But whatever the queueing mechanism is, is broken at least for websockets and large messages. My messages are ~2MB.
There is a problem when a large (>345 kB) message is being written to a websocket. The connection will actually time out, unless this
while
is in place. Unfortunately, this pretty much busy-waits. But whatever the queueing mechanism is, is broken at least for websockets and large messages. My messages are ~2MB.Without this, your connection will be dropped by the remote side. Tested with C++
qtwebsockets
and Pythonwebsockets
clients.The two part write()/handleRemaining() does not seem to handlw when handleRemaining() still has remaining properly.