I've made start on refactoring the WebSocket implementation to go directly to the SocketWrapper - bypassing the Servlet[Input|Output]Streams. [1]
This is very much a work in progress. Currently, all bar one of the WebSocket unit tests pass although some tests seem to be taking longer as they should. The main advantage of this refactoring that blocking writes can go directly to the SocketWrapper. This will remove the need for two container threads (one reading and one writing thread) working with the socket at the same time. I haven't started this refactoring yet. I'll merge this back to trunk once I have something that: a) I'm happy is heading in the right direction b) Passes the unit tests c) Passes the Autobahn tests I'm currently mulling over the best way to handle the blocking writes. My current ideas revolve around signalling that a blocking write is required by passing a null SendHandler. Mark [1] https://github.com/markt-asf/tomcat/tree/markt-trunk --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
