I'm trying to wrap my head around a design decision in x509_certificate. The class provides two factory functions that keep a cache of certs. If a cert is requested, and it's already in the cache, the cached version is used.
But we also provide a destructor, which removes the cert from the cache. So is the caller to the factory function supposed to call the destructor of the x509_certificate pointer that it gets back from the factory, or not? If so, then we have a ref-counting problem, where we'll die on the second person to release a uniqued cert. If not, we just cache forever, but then why provide a destructor? Avi --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
