Messages issued by user may get caught in buffer?

[endtwist]

When a user issues a message or notification, it seems as though it gets caught in a buffer/queue going back to that user. This may also happen with other types of notifications. Any messages in the queue should be sent when there is an available connection; check for some sort of race condition or similar?

[endtwist]

It seems like it might be a case of more than one message being pushed to the session's "connection" response manager. Since this is supposed to be only used for immediate responses to current connections, either the conflict needs to be found or responses need to be handled differently.

[endtwist]

Seems to be happening in Room#join, which is calling Room#send. Agent#respond is called in join, then again in send, causing items to be queued into the buffer for connection responses.