Ah, in doing a little bit more thinking I realize there is some unfortunate
naivete (OK ignorance) in my original post, so let me clarify.
I should not have focussed on *parsing* of the full HTTP Request. Of course
that has to be 'deferred' at some level (think SOAP, file uploads, and of
course we all do HttpRequest.setCharacterEncoding('UTF-8') in a filter,
right?)
I'm really just interested in the reading of the socket's *bytes*. Does the
servlet spec proscribe a container from reading all of the bytes in the http
request before handing it off to the application (filter, servlet, et al)?
It seems to me that to gain the full benefits from NIO, you want
non-blocking, selector-based reads of all of the socket's bytes until the
end of the http request is identified.
I will look at the servlet spec as well
--
View this message in context:
http://tomcat.10.n6.nabble.com/Getting-my-head-around-NIO-simulated-blocking-trying-to-tp4996773p4996775.html
Sent from the Tomcat - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
