On 26/03/2014 14:08, Rémy Maucherat wrote: > 2014-03-26 14:52 GMT+01:00 Mark Thomas <ma...@apache.org>: > >> Yes, it is a solvable problem as long as you drop the self-imposed >> requirement to run on top of the Servlet API. Now the difficulties are >> understood, I'm beginning to think about dropping that requirement and >> using some of the Tomcat internals directly. The blocking/non-blocking >> gets a whole lot easier very quickly if you do that. >> > Ok. I don't think it would make much difference in the container code > since the upgrade mode is light already and all it needs is to pass down a > "block" flag, but your websocket impl would be able to shed its simulated > blocking.
I agree completely. I'm becoming less convinced that benefit of running on any container is worth the price of the complexity that the simulated blocking introduced. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
