On 31/01/2014 07:58, Yann Simon wrote: >>>> On Jan 30, 2014, at 11:18 AM, Yann Simon <yann.simon...@gmail.com>
>>>>> I wrote a sample app to demonstrate the problem: >>>>> https://github.com/yanns/servlet31_async Thanks for the sample. That always makes looking at these things a lot easier. > Maybe it is too simplified in my head but I though if tomcat permits to > exit the onDataAvailable immediately and to read the input afterwards, as I > am doing in the sample app, then it is possible. The Servlet specification is not always as clearly written as it could be. As one of the EG members, that is partly my fault. I wasn't too involved in the the non-blocking discussions as other EG members were for more experienced than me with non-blocking at the time. I don't recall anything that would not permit what you are trying to do but I'd need to double check that. I'd need to check the archives to see if there was anything there that didn't make the specification document. > Jetty seems to allow this. Why not tomcat? Is there something in the > specification about it. I could not find anything explicit. It could simply be a bug in Tomcat. I've had a quick look and I think I might have a fix (thanks to Remy for the hint earlier in the thread) but the non-blocking code has proved tricky to get right and I want to do some more testing. I should get to that later today. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
