Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 11497 invoked by uid 6000); 27 Apr 1998 10:10:16 -0000 Received: (qmail 11488 invoked from network); 27 Apr 1998 10:10:14 -0000 Received: from twinlark.arctic.org (204.62.130.91) by taz.hyperreal.org with SMTP; 27 Apr 1998 10:10:14 -0000 Received: (qmail 6722 invoked by uid 500); 27 Apr 1998 10:10:14 -0000 Date: Mon, 27 Apr 1998 03:10:14 -0700 (PDT) From: Dean Gaudet To: new-httpd@apache.org Subject: Re: apache-nspr-01.tar.gz In-Reply-To: Message-ID: X-Comment: Visit http://www.arctic.org/~dgaudet/legal for information regarding copyright and disclaimer. 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 Mon, 27 Apr 1998, Alexei Kosut wrote: > On Mon, 27 Apr 1998, Dean Gaudet wrote: > > > - buffered i/o: > > They don't have any buffered I/O... I'm trying to figure out the > > cleanest way to put BUFFs on top of the layers. I'll probably make > > the buffering a layer itself... but there's no flush function to > > run down the layers. [...] > Take the NSPR layers, and put our BUFF code on top of them. i.e., make all > layers (optionally) buffered, and define mechanisms to flush and do other > such things to them. You've said almost exactly what I said, except my solution is probably more general. To use your terminology, buffering is a filter. When you don't need it you don't push it on the stack. When you need it, you push a buffering layer underneath your code. By default the top of the stack will always have a buffer (but maybe we want to change that eventually, right now I'm not changing that until I get a working server). Buffering is not required on static-only servers, and proxy caches for example. So it's not strictly necessary. But it is desirable for flexibility. Dean