Re: configure HTTP1.1 pipline depth on Tomcat 5.0
OK my knowledge was weak and I am also not an expert on TC internals. But pipelining makes only sense when the requests could be useful parallel processed (e.g. CPU intensive and more CPU's available) and do not depend on each other. The responses must be delivered anyhow in incoming sequence. And the client has the task of matching responses to requests. - Original Message - From: Caldarale, Charles R [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Saturday, June 25, 2005 6:06 PM Subject: RE: configure HTTP1.1 pipline depth on Tomcat 5.0 From: Caldarale, Charles R Subject: RE: configure HTTP1.1 pipline depth on Tomcat 5.0 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. To answer my own question, the serialization of requests occurs in: org.apache.coyote.http11.Http11Processor where there's a loop in the process() method that insures each pipelined request is responded to before starting on the next. Note that this is a serialization of processing, not accepting, so there does not appear to be any limit on the number of requests that can be pipelined together in a single transmission. There is a configurable limit on the number of keep alives that will be tolerated on an otherwise idle connection. - 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] ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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. And so TC will also not accept another request before it processed the last Karl-Heinz - Original Message - From: Feng Xie (fxie) [EMAIL PROTECTED] Hi, Is there any way to configure HTTP1.1's persistent connection's pipeline length on Tomcat 5.0 ? By pipeline length, I mean the number of HTTP request could be sent by the HTTP/1.1 client before it gets back the first response. Thanks in advance, Feng ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: configure HTTP1.1 pipline depth on Tomcat 5.0
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]
RE: configure HTTP1.1 pipline depth on Tomcat 5.0
From: Caldarale, Charles R Subject: RE: configure HTTP1.1 pipline depth on Tomcat 5.0 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. To answer my own question, the serialization of requests occurs in: org.apache.coyote.http11.Http11Processor where there's a loop in the process() method that insures each pipelined request is responded to before starting on the next. Note that this is a serialization of processing, not accepting, so there does not appear to be any limit on the number of requests that can be pipelined together in a single transmission. There is a configurable limit on the number of keep alives that will be tolerated on an otherwise idle connection. - 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]
configure HTTP1.1 pipline depth on Tomcat 5.0
Hi, Is there any way to configure HTTP1.1's persistent connection's pipeline length on Tomcat 5.0 ? By pipeline length, I mean the number of HTTP request could be sent by the HTTP/1.1 client before it gets back the first response. Thanks in advance, Feng
