On 8/19/07 11:34 AM, Peter Karman wrote: > John Siracusa wrote on 8/18/07 11:25 PM: >> Although I don't want this (caching, etc.) to be part of the behavior of >> Rose::DB->new(), I'm not opposed to making a new method called, say, >> Rose::DB->new_or_existing() or Rose::DB->new_or_cached(). > > new_or_cached() sounds like a great idea. Perhaps also a clear_cache() method, > to help with the mod_perl startup issue mentioned here? > > http://article.gmane.org/gmane.comp.lang.perl.modules.dbi.rose-db-object/1802/ > match=karman > > Or perhaps there's a better way to handle that issue.
There'd definitely be cache-clearing and inspection methods, but the mod_perl pre-fork issue would be handled automatically by checking the ServerStarting global in whatever package (I forget the details). -John ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object