On 8/18/07 11:56 PM, Peter Karman wrote: > Given that caching of database connections (either by caching Rose::DB objects > or the DBI objects they hold) is an oft-repeated thread on this list, and > given that John (quite rightly imo) doesn't want to put the caching behaviour > into Rose::DB, I wonder if it would be worthwhile to have a > Rose::DB::Persistent (Rose::DB::Cached?) subclass that does have smart object > caching by default.
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(). -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
