Please advise if I should set timeout differently. At the very least, the queue com.codeminders.socketio.server.transport.XHRTransportConnection#packets should probably have limited capacity. Maybe even the session could disconnect when the queue becomes full because that means the browser does not read messages
... which can easily lead to a memory-leak-like behavior if the client opens session using xhr-polling but does not actually poll.
I set the timeout in the
onConnect()
listener:Please advise if I should set timeout differently. At the very least, the queue
com.codeminders.socketio.server.transport.XHRTransportConnection#packets
should probably have limited capacity. Maybe even the session could disconnect when the queue becomes full because that means the browser does not read messages