httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralf S. Engelschall" <>
Subject Re: [PATCH] Shared Memory Pools ;-)
Date Mon, 25 Jan 1999 17:15:00 GMT

In article <> you wrote:
> Ralf S. Engelschall writes:

>>Since years I was annoyed of the fact that our pre-forked process model
>>basically means that every server lives it's own life (= address space) and
>>this way module authors cannot easily spread module configuration or other
>>data accross the processes. For most of the modules that's no real problem.
>>But it gets nasty when you want to write for instance a mod_traffic which
>>counts in real-time the traffic of Apache.  Or a mod_bandwidth which thottles
>>the total used bandwidth of Apache.  

> Go for it.

>>Idea and Proposed Solution

> Very nice, as usual.  Read only access would be good.

You mean an argument to ap_acquire_lock() which says whether you want to
acquire it for read-only or read-write, right?

> Code that doesn't get checked in disappears, so I'd like to
> see this go into the 1.3 family.

<grin> That's why I posted it for Apache 1.3.5... ;-)

                                       Ralf S. Engelschall

View raw message