Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 2416 invoked by uid 500); 2 May 2001 13:45:55 -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 2389 invoked from network); 2 May 2001 13:45:53 -0000 Date: Wed, 2 May 2001 06:47:22 -0700 (PDT) From: X-Sender: To: Luke Kenneth Casson Leighton Cc: , , Subject: Re: APR shared memory requirements. In-Reply-To: <20010502152243.N11551@angua.rince.de> 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 Wed, 2 May 2001, Luke Kenneth Casson Leighton wrote: > On Tue, May 01, 2001 at 08:49:43AM -0700, rbb@covalent.net wrote: > > > > Most people have realized that APR's shared memory support isn't good > > enough to support Apache, or in reality most other applications. We had > > this discussion during the hack-a-thon, and we came up with a small list > > of requirements for APR's new shared memory implementation. Here are the > > notes: > > > > 1) malloc-like implementation > > 2) Anonymous and Key based shared memory support > > 3) Def-ref macros (these must use double indirection) > > 4) Reference counting > > 5) Cleanups that use the pool implementation > > sander, elrond and i have written up a stackable memory system. > > we were waiting for an opportunity to present it to you [apr] > such that it would be received. > > > the stackable memory system basically allows one memory-allocation > system to allocate memory from another. > > [not like the pool system, which is just a means to allocate > memory from the system library (malloc/free), and to associate > cleanup routines with it] > > there is nothing to stop you, or anyone, from writing a > shared memory library that conforms to the SMS api. > > there is nothing to stop anyone from modifying apr_pool* to > conform to the SMS api. > > in this way, you could pass in a shmem-SMS-parent allocator > to apr_pool_create(), and it will create a shared memory > pool that looks, to all intents and purposes, like an apr_pool_t. > > interested? Oh yeah! Could you point the APR developers to where this is implemented, or post a patch? I think this would be REALLY cool to get into APR, because it would solve most, if not all, of our memory handling needs. Ryan _______________________________________________________________________________ Ryan Bloom rbb@apache.org 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------