Received: (from majordom@localhost) by hyperreal.com (8.8.5/8.8.5) id PAA12976; Thu, 12 Jun 1997 15:37:36 -0700 (PDT) Received: from devsys.jaguNET.com (devsys.jaguNET.com [206.156.208.6]) by hyperreal.com (8.8.5/8.8.5) with ESMTP id PAA12937 for ; Thu, 12 Jun 1997 15:37:30 -0700 (PDT) Received: (from jim@localhost) by devsys.jaguNET.com (8.8.5/jag-2.4) id SAA24990 for new-httpd@apache.org; Thu, 12 Jun 1997 18:37:25 -0400 (EDT) From: Jim Jagielski Message-Id: <199706122237.SAA24990@devsys.jaguNET.com> Subject: Re: Missing headers for small requests? To: new-httpd@apache.org Date: Thu, 12 Jun 1997 18:37:25 -0400 (EDT) In-Reply-To: from "Alexei Kosut" at Jun 12, 97 02:11:24 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Alexei Kosut wrote: > > On Thu, 12 Jun 1997, Dean Gaudet wrote: > > > It's been proposed several times. But needs a revamp of the i/o system to > > do it... hey can we agree that we want to use sfio? If so then someone > > can get working on integrating sfio. > > It's always been my plan to integrate an IO package like sfio into > Apache 2.0. However, is sfio itself the best choice? While I've not > heard anything specific (nor have I checked specifically), I've heard > random things in passing that seem to indicate there are problems with > sfio. RST used sfio in an early apache-XX, then switched over to > bstdio. > I think RSTs reason for the switch was the bstdio was more portable than sfio, esp when one considers the configuration tool ('iff'?) used to do the initial configs. Also, bstdio seemed a LOT faster. I think that the sfio/bstdio/whatever debate is still up in air. The consensus is that we need our our stdio routines, but not which is best. -- ==================================================================== Jim Jagielski | jaguNET Access Services jim@jaguNET.com | http://www.jaguNET.com/ "Look at me! I'm wearing a cardboard belt!"