I'm quite aware the code is public, but I thought it would be highly
recommended to rely on interfaces rather than copying & pasting
implementations that might change in future.
Days ago I put on this list a question (that went unanswered) concerning
the proper way to infer the running mpm nam
On 05.03.2012 11:33, Massimo Manghi wrote:
On 03/03/2012 07:04 PM, Rainer Jung wrote:
On 02.03.2012 00:34, Sorin Manolache wrote:
On 03/02/12 00:21, Ben Noordhuis wrote:
On Thu, Mar 1, 2012 at 17:29, wrote:
Hello,
I would need a memory buffer associated per worker thread (in the
worker
MPM)
On 03/03/2012 07:04 PM, Rainer Jung wrote:
On 02.03.2012 00:34, Sorin Manolache wrote:
On 03/02/12 00:21, Ben Noordhuis wrote:
On Thu, Mar 1, 2012 at 17:29, wrote:
Hello,
I would need a memory buffer associated per worker thread (in the
worker
MPM) or to each process (in the prefork MPM).
On 02.03.2012 00:34, Sorin Manolache wrote:
On 03/02/12 00:21, Ben Noordhuis wrote:
On Thu, Mar 1, 2012 at 17:29, wrote:
Hello,
I would need a memory buffer associated per worker thread (in the worker
MPM) or to each process (in the prefork MPM).
In order to do that, I would need a map thread
On 03/02/12 00:21, Ben Noordhuis wrote:
On Thu, Mar 1, 2012 at 17:29, wrote:
Hello,
I would need a memory buffer associated per worker thread (in the worker
MPM) or to each process (in the prefork MPM).
In order to do that, I would need a map thread<->buffer. So, I would
need a sort of thread
On Thu, Mar 1, 2012 at 17:29, wrote:
> Hello,
>
> I would need a memory buffer associated per worker thread (in the worker
> MPM) or to each process (in the prefork MPM).
>
> In order to do that, I would need a map thread<->buffer. So, I would
> need a sort of thread ID/key/handle that stays the
