----- Original Message ----- From: "Costin Manolache" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, July 12, 2003 8:41 AM Subject: Re: [5.0] [PROPOSAL] Make output buffer size limit configurable
> Remy Maucherat wrote: > > > Bill Barker wrote: > >>>How about making the output buffer size limit configurable? > >>>(A value of "-1" could mean indefinite growth, if people know what they > >>>are doing.) > >> > >> I also dislike the proposal, but since it's configurable, and off by > >> default > >> I can limit myself to -0. The biggest problem I see is that "if people > >> know what they are doing", then they would never dream of enabling the > >> option :). > > > > I will vote -1 to the proposal: > > - this has no actual performance benefits that I can see > > - this is equivalent to a "benchmark" flag, where the server is slightly > > faster, but isn't useful for anything but throughtput testing (since the > > server would eventually just die) > > > > Do you see such a benchmark setting in the HTTPd ? I think not. > > I have nothing about people optimizing code, but the optimizations > > should have an actual usefulness (such as tag pools, which some people > > like). If the optimization makes the server unusable, then it shouldn't > > be there. > > > It can also be useful if you have a client that doesn't support "chunked > encoding" - which is probably true for a _lot_ of scripting tools. > If there is any other way to have the response not use chunked encoding, > then I agree this is not needed. > > Do we still support HTTP/1.0 or some request header to disable the encoding? > AFAIK, the HTTP/1.0 support for Tomcat-Coyote-Standalone is nearly identical to Apache/httpd. > Costin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments. In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
