Hi Stefan,

On Fri, Mar 20, 2015 at 10:12 AM, Stefan Eissing
<stefan.eiss...@greenbytes.de> wrote:
> Just for the record: the important thing to learn for me was that there is 
> another layer underneath apr_pool_t
> called apr_allocator_t which is not  thread-safe by default - but can be made 
> so. With my own allocator per
> real connection and a mutex protecting it, I can pool and subpool to my 
> heart's content across threads.

While pool (allocator) allocations are not thread-safe, creating a
subpool is, and each thread can than use its own pool (this model is
often used with APR pools).

This tells nothing about pool allocated objects' lifetime though
(accross/after threads), so maybe can you describe a bit more (but
less than the code ;) which object has its own or shared pool, with
regard to http/2 model (request/stream/connection/frame)?

That would help (at least me) to determine where locking is needed or
not (thanks to subpools).

Anyway, thanks for this code which looks/is very promising!

Regards,
Yann.

Reply via email to