Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 47170 invoked by uid 500); 23 May 2001 00:25:46 -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 47069 invoked from network); 23 May 2001 00:25:33 -0000 Date: Tue, 22 May 2001 17:27:21 -0700 (PDT) From: X-Sender: To: Subject: Re: Installing alternate transports in Apache 2.0 In-Reply-To: <20010522154842.A2501@waka.ebuilt.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Tue, 22 May 2001, Roy T. Fielding wrote: > > WIBNIF we reintroduced the notion of a network layer IOL? For the above > > mentioned SSL API, we would insert the appropriate IOL during the > > pre_connection phase. The core filter would use iol_read, iol_write, etc. > > to do the network i/o. Thoughts? > > How is that different from swapping the bottom filter (doing normal write, > writev, sendfile) with an SSL filter (doing ssl_write)? The main difference is that currently conn_rec's have an apr_socket_t in them. If we really wanted to abstract this just using filters, that would need to move to a void *, so that modules could store arbitrary types of structures in it. Ryan _______________________________________________________________________________ Ryan Bloom rbb@apache.org 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------