Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 21227 invoked by uid 500); 12 Nov 2000 04:27:35 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 21216 invoked from network); 12 Nov 2000 04:27:34 -0000 Date: Sat, 11 Nov 2000 20:28:58 -0800 (PST) From: rbb@covalent.net X-Sender: rbb@koj.rkbloom.net To: new-httpd@apache.org cc: cliffwoolley@yahoo.com Subject: RE: Implementing split() on pipe buckets? In-Reply-To: <002201c04c60$6a116470$92c0b0d0@roweclan.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > I figured out, Ryan is inside the bucket, so he's looking for the > most optimized way for buckets to do their thing. Some people are > inside the filter, and they are looking for the simplest way for > filters to do their thing. The answer is really somewhere in the > middle, and I'm not suggesting I even know where that middle is. Actually, I'm in the middle. I want clean code, which is one of the reasons I don't want reading from the file to keep us from being able to use sendfile. I almost think we need a peek function. But I also want code that makes sense, and in the case of pipes and sockets, splitting them doesn't make any sense. Ryan _______________________________________________________________________________ Ryan Bloom rbb@apache.org 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------