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? Also any reason to put the structure in ssl_private.h rather than the .c file directly? joe