> From: charly [mailto:[EMAIL PROTECTED] > Subject: Re: configure HTTP1.1 pipline depth on Tomcat 5.0 > > AFAIK the "pipeline length" cannot be more than one by design. > No client will send another request before it received the > response from the last.
To quote from RFC 2616 (section 8.1.1): "HTTP requests and responses can be pipelined on a connection. Pipelining allows a client to make multiple requests without waiting for each response, allowing a single TCP connection to be used much more efficiently, with much lower elapsed time." And in 8.1.2: "A significant difference between HTTP/1.1 and earlier versions of HTTP is that persistent connections are the default behavior of any HTTP connection. That is, unless otherwise indicated, the client SHOULD assume that the server will maintain a persistent connection, even after error responses from the server." > And so TC will also not accept another request before it > processed the last Can you tell us where in the Tomcat code such a restriction is implemented? I haven't been able to find it, although I'm certainly not an expert on Tomcat internals. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
