Received: by taz.hyperreal.com (8.7.6/V2.0) id FAA16598; Mon, 14 Oct 1996 05:31:25 -0700 (PDT) Received: from shado.jaguNET.com by taz.hyperreal.com (8.7.6/V2.0) with ESMTP id FAA16592; Mon, 14 Oct 1996 05:31:24 -0700 (PDT) Received: (from jim@localhost) by shado.jaguNET.com (8.8.0/jag-2.3) id IAA26341 for new-httpd@hyperreal.com; Mon, 14 Oct 1996 08:31:22 -0400 (EDT) From: Jim Jagielski Message-Id: <199610141231.IAA26341@shado.jaguNET.com> Subject: Re: WWW Form Bug Report: "Hard-coded 150 connection limit not documented " on FreeBSD (fwd) To: new-httpd@hyperreal.com Date: Mon, 14 Oct 1996 08:31:21 -0400 (EDT) In-Reply-To: <9610140956.aa03127@gonzo.ben.algroup.co.uk> from "Ben Laurie" at Oct 14, 96 09:56:54 am X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com Ben Laurie wrote: > > Rob Hartill wrote: > > > > > > This has become a frequent complaint/request. > > I haven't quite understood why this limit is hard? Is there any reason not to > make it soft? > I haven't looked too closely at it... I'm guessing that it's only on the file-version of the scoreboard that it would be a concern doing a "on-the-fly" malloc of the space, and even then it's a simple matter of when it's done... -- Jim Jagielski << jim@jaguNET.com >> | "If we took the bones out ** jaguNET Access Services ** | it wouldn't be crunchy" Email: info@jaguNET.com | Whizzo Crunchy Frog ++ http://www.jaguNET.com/ +++ Voice/Fax: 410-931-3157 ++