Date: Sun, 24 Jan 1999 12:55:21 +0100
From: "Ralf S. Engelschall" <rse@engelschall.com>
To: new-httpd@apache.org
Subject: Re: [APR] Comments to proposed function interface
Message-ID: <19990124125521.A20932@engelschall.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Organization: Engelschall, Germany.
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org


In article <19990122131551.14267@hyperreal.org> you wrote:

> Okay, here are some thoughts I just had to write down when I
> first read the apr-function.txt draft.
>[...]

I've also quickly looked over the apr-function.txt draft and I was astonished
to now find anything about some abstraction to memory allocation.  I expected
to read something about a pool system like our current one but which is able
to both allocate pool data from the heap and from shared memory areas in a
portable way. Because that's what I've already written for my EAPI in the
background and my understanding always was that this functionality should be
already provided by a low-level API like APR and not at higher levels. For the
heap based allocation POSIX malloc() & friends could be used internally by
APR, of course. But the dirty work with various mmap()-based or shmget()
variants should be done by APR.
                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com