Improvement Request: Support for Slow Client

[lpage30]

If you have several clients and one is slower than the others you may want to 'cut them off' or do something else to prevent others from being impacted.

Several approaches to this, with the code as of this writing it could be done via async call back.
It would be nice to extend the architecture to address this issue more completely 'out of the box' with some config/tuning params.

[mrniko]

Please provide more details about your vision of this feature.

[lpage30]

The concept of a slow client is that browser that is not handling data as fast as others and the PacketQueue for that client starts to grow.
As a knee jerk 'gut' approach we are establishing a ceiling for the queue size, and on every msg send checking all the client queue sizes and dropping them outright if their queue is larger than the ceiling.
Other more delicate approaches might be similar to those implemented by ActiveMQ (http://activemq.apache.org/slow-consumer-handling.html) which is pretty involved.

[pramodbms]

@mrniko Are we planning to implement this feature in the near future? It would be a "No-GO" without this feature as we are sending time sensitive data to the clients. For a slower client, we would like to send the latest data by throttling at the server side. Will there be any event raised for slow clients?[similar to a BlockedHandler or some thing] ?

[pramodbms]

@mrniko some thing like the first answer @ : http://stackoverflow.com/questions/28862613/throttling-websockets-with-netty-socketio-server