On 2/28/2012 4:08 AM, Mark Thomas wrote:
WebSocket is working with good performance and passing all Autobahn
tests on BIO, NIO and APR.
Currently, all three connectors using blocking IO throughout so there is
a one to one mapping between threads and connections. Therefore,
scalability is not what it could be for NIO and APR.
The remaining TODOs are:
Essential:
a) move to non-blocking between messages
b) address the threading issues around message sending
c) add some documentation
Nice to haves:
- better examples (Petr Praus, Jonathan Drake& Slávka are working on a
chat application)
- non-blocking throughout for NIO (requires much more state to be
maintained and a change to the API - not sure it is worth it)
I did this for Comet in the sandbox, and it is totally doable. But in my opinion, it's not worth the effort. It is much easier to just
increase the buffer size at the network level, and voila, it wont block. I can't imagine WebSocket's message based system would be using
very large messages, it's definitely not suited for that.
Since there is a possibility that a) will require some changes to the
upgrade code, I am holding off on porting that to 7.0.x for now.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
