httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Plüm, Rüdiger, VF-Group" <ruediger.pl...@vodafone.com>
Subject Re: [PATCH] Dynamic locking upcalls in mod_ssl
Date Thu, 21 Aug 2008 11:49:35 GMT
 

> -----Ursprüngliche Nachricht-----
> Von: Joe Orton 
> Gesendet: Donnerstag, 21. August 2008 13:41
> An: dev@httpd.apache.org
> Betreff: Re: [PATCH] Dynamic locking upcalls in mod_ssl
> 
> On Wed, Aug 20, 2008 at 10:36:37AM -0400, Sander Temme wrote:
> >
> > On Aug 18, 2008, at 5:18 AM, Joe Orton wrote:
> >
> >> So generally pconf is the right pool to use, along with a cleanup
> >> registered against that pool which sets the callbacks to NULL.
> >
> > Yes, with the cleanup it no longer hangs.  What about 
> stashing a pool  
> > reference in a global, is that a red flag?
> 
> Given that the lifetime of the callbacks is now constrained, 
> is the new 
> global pool still needed?

Where does this patch use a global pool? It keeps a reference on the pconf
pool in a global variable, but it no longer creates a global pool.
Or do I miss your point?

Regards

Rüdiger

Mime
View raw message