This is a clone of Apache httpd 2.0.35. I just considered it easier to clone than to search the archives (I'm not subscribed to the httpd mailing list) for why they do it this way. In particular, I can't see why I need 5Min to do an ACK on the first request.
In light testing, the setSoTimeout seems to be cheap. Will need more O/Ss to be sure. It could also be fixed in the filters if they limit the number of bytes that could be requested at once. ----- Original Message ----- From: "Remy Maucherat" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Thursday, April 25, 2002 10:17 PM Subject: Re: cvs commit: jakarta-tomcat-connectors/http11/src/java/org/apache/coyote/http11 Http11Processor.java Http11Protocol.java > > billbarker 02/04/25 18:50:32 > > > > Modified: http11/src/java/org/apache/coyote/http11 > > Http11Processor.java Http11Protocol.java > > Log: > > Fix problem with soTimeout. > > > > The makes Coyote act like httpd with respect to soTimeout (which is what > it was trying to do before, but only worked on HTTP/1.0 connectors). > > So the SoTimeout was overwritten ... You actually call setSoTimeout *a lot*. > This is more flexible, since you can configure separately the connection > timeout, but unless that call is free or almost free, this is not a good > idea IMO. > > Remy > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
