Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 2609 invoked by uid 500); 28 Jun 2002 19:56:54 -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 2589 invoked from network); 28 Jun 2002 19:56:54 -0000 Errors-To: Message-Id: <5.1.0.14.2.20020628145626.02ad4c38@pop3.rowe-clan.net> X-Sender: wrowe%rowe-clan.net@pop3.rowe-clan.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 28 Jun 2002 14:58:31 -0500 To: Brian Pane From: "William A. Rowe, Jr." Subject: Re: Breaking something? Now is the time? Cc: dev@apr.apache.org In-Reply-To: <3D1CB4CD.3090803@cnet.com> References: <5.1.0.14.2.20020628092316.01ed5ad8@pop3.rowe-clan.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Rating: 209.66.108.5 1.6.2 0/1000/N At 02:11 PM 6/28/2002, Brian Pane wrote: >I want to break something: binary compatibility for the pool API. > >This has been on my list for a long time, but I haven't yet had >time to implement it. What you are describing is [was] SMS. Even with the opaque structure, we are still facing derefs that will significantly alter performance. Definately look in CVS's attic for the original implementation to start with. We don't have the time to implement this in the current Apache release cycle [2.0.40] given the issues people raised with the original SMS implementation. I suggest that -if- we prove this is viable, we introduce it with the rollout of version 1.0. Bill