-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Olaf,
On 12/27/2010 5:24 PM, Olaf Tomczak wrote: > 2010/12/27 Christopher Schultz <ch...@christopherschultz.net> >> Non-blocking just means that your request processor threads don't block >> waiting for data to arrive. The requirements of reading the request -- >> including all the headers -- do not change with the connector. Tomcat >> needs to read the entire set of headers in order to route the request to >> the right host and webapp. Also, Tomcat must have all headers in order >> to perform some operations -- such as responding to "getHeaders" calls >> which sometimes require that multiple separate HTTP header lines be >> merged into a single method return value. > > I understand that the whole request must be read to start "request > processing" - I was just suggesting that from what I understand the > connector does not wait for the buffer to be completely filled before > starting to parse request line and headers. Isn't that right? I don't believe the difference you describe would be detectable at any level. The choice of connector does not change the logic for request processing: only that of gathering the bytes from the request. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0ZGxMACgkQ9CaO5/Lv0PCygACgv66l6yc6Wubf/szFbfgOm90B nEgAoI/MAXqpieNtwKr3p389EV6lyQy5 =MsJZ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
