Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 22444 invoked by uid 6000); 20 Oct 1999 21:09:53 -0000 Received: (qmail 22335 invoked from network); 20 Oct 1999 21:09:48 -0000 Received: from nebula.lyra.org (gstein@216.98.236.100) by taz.hyperreal.org with SMTP; 20 Oct 1999 21:09:48 -0000 Received: from localhost (gstein@localhost) by nebula.lyra.org (8.9.3/8.9.3) with ESMTP id OAA24941 for ; Wed, 20 Oct 1999 14:10:20 -0700 Date: Wed, 20 Oct 1999 14:10:19 -0700 (PDT) From: Greg Stein To: new-httpd@apache.org Subject: Re: MMAP In-Reply-To: <005301bf1b3c$b56cd720$0a1aa8c0@jetnet.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Well, the outcome is that we beat Ryan into submission. Of course. :-) I'd go for #2 also. Breakage at compile/link time is loads easier to deal with than at runtime. Cheers, -g On Wed, 20 Oct 1999, David Reid wrote: > I read most of the other thread but still managed to get lost as to it's > eventual outcome :-) > > ----- Original Message ----- > From: Manoj Kasichainula > To: > Sent: 20 October 1999 21:48 > Subject: Re: MMAP > > > > On Wed, Oct 20, 1999 at 09:26:52PM +0100, David Reid wrote: > > > For platforms that don't support MMAP what should I do? I have 2 > > > thoughts... > > > > > > 1) provide the "standard" no-op functions > > > 2) provide nothing for platforms that don't support MMAP > > > > For reasons I've talked about in another thread, I'd pick #2, along > > with a feature macro like Ben talked about. > > > > -- > > Manoj Kasichainula - manojk at io dot com - http://www.io.com/~manojk/ > -- Greg Stein, http://www.lyra.org/