Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 60595 invoked by uid 500); 8 Nov 2001 17:51:10 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 60584 invoked from network); 8 Nov 2001 17:51:10 -0000 Date: Thu, 8 Nov 2001 09:51:12 -0800 From: Justin Erenkrantz To: Bill Stoddard Cc: APR Development List Subject: Re: [PATCH] APR Socket IOL Message-ID: <20011108095112.W11988@ebuilt.com> References: <01aa01c1686a$9d144d20$0d381b09@sashimi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01aa01c1686a$9d144d20$0d381b09@sashimi> User-Agent: Mutt/1.3.22.1i X-AntiVirus: scanned for viruses by AMaViS 0.2.1-pre3 (http://amavis.org/) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Thu, Nov 08, 2001 at 10:32:45AM -0500, Bill Stoddard wrote: > This patch is a first rough implementation of a socket iol in APR (from discussions with > Sander Striker a few months back). > > Public API Changes: > No new APIs were created. > apr_socket_create() has an extra parameter, a pointer to an apr_socket_iol_t. > > New Public Structures: > apr_socket_iol_t - contains pointers to callback functions. > > Usage: > If you do not want to redirect socket calls and just use existing APR calls, use > apr_socket_create() thusly: > apr_socket_create(&new_sock, APR_INET, SOCKSTREAM, NULL, r->pool); I thought we were trying to move away from function pointers because people thought they were slow. Could/should we create a parallel API for this instead? -- justin