Return-Path: <new-httpd-owner-new-httpd-archive=hyperreal.org@apache.org>
Delivered-To: new-httpd-archive@hyperreal.org
Received: (qmail 3433 invoked by uid 6000); 8 Mar 1998 06:04:10 -0000
Received: (qmail 3427 invoked from network); 8 Mar 1998 06:04:09 -0000
Received: from valis.worldgate.com (marcs@198.161.84.2)
  by taz.hyperreal.org with SMTP; 8 Mar 1998 06:04:09 -0000
Received: from localhost (marcs@localhost)
	by valis.worldgate.com (8.8.7/8.8.7) with SMTP id XAA20770
	for <new-httpd@apache.org>; Sat, 7 Mar 1998 23:04:06 -0700 (MST)
Date: Sat, 7 Mar 1998 23:04:05 -0700 (MST)
From: Marc Slemko <marcs@worldgate.com>
To: new-httpd@apache.org
Subject: Re: cvs commit: apache-2.0/docs page_io
In-Reply-To: <Pine.LNX.3.96dg4.980307220525.24934I-100000@twinlark.arctic.org>
Message-ID: <Pine.BSF.3.95q.980307230327.23977I-100000@valis.worldgate.com>
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

On Sat, 7 Mar 1998, Dean Gaudet wrote:

> 
> 
> On Sat, 7 Mar 1998, Marc Slemko wrote:
> 
> > But yes, we do need some explicit support for the concept of going from a
> > descriptor to the network without copys.  I don't see that as being a bad
> > thing.
> 
> Oh no I don't see it as bad either... I'm just mumbling.  But where I'm
> wondering how things will work is say you've got a filter in the stack
> which does crypto using an external crypto card, it may be able to
> implement transmitfile in a few different ways depending on whether the
> layer below it supports transmitfile...

Erk.  Well.  That does indeed get interesting.  You could have one hell
of a cute system there.  <g>