Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 36395 invoked from network); 12 Jul 2003 15:40:47 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 12 Jul 2003 15:40:47 -0000 Received: (qmail 24347 invoked by uid 97); 12 Jul 2003 15:43:17 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@nagoya.betaversion.org Received: (qmail 24340 invoked from network); 12 Jul 2003 15:43:16 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 12 Jul 2003 15:43:16 -0000 Received: (qmail 35377 invoked by uid 500); 12 Jul 2003 15:40:38 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 35319 invoked from network); 12 Jul 2003 15:40:38 -0000 Received: from main.gmane.org (80.91.224.249) by daedalus.apache.org with SMTP; 12 Jul 2003 15:40:38 -0000 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19bMTU-0002N8-00 for ; Sat, 12 Jul 2003 17:39:48 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: tomcat-dev@jakarta.apache.org Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19bMTT-0002Mz-00 for ; Sat, 12 Jul 2003 17:39:47 +0200 From: Costin Manolache Subject: Re: [5.0] [PROPOSAL] Make output buffer size limit configurable Date: Sat, 12 Jul 2003 08:41:07 -0700 Lines: 34 Message-ID: References: <3F0D91E3.2070606@sun.com> <3F0DDF63.30802@apache.org> <3F0EEFAD.9020702@sun.com> <009201c347e9$1dba0c30$ec66a8c0@bbarkerxp> <3F0FB704.1060307@apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@main.gmane.org User-Agent: KNode/0.7.2 Sender: news X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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? Costin --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org