On Tue, Dec 21, 2010 at 7:26 AM, Tommy Butler <[email protected]> wrote:
> The article mentions the caching of session storage and arbitrary key-value > pairs, and does so with a clear demonstration that these two features rely > on the memcached backend. But for what I'm most interested in (the caching > of DBIx objects) there's no evidence in the article at all that the > mentioned "DBIx::Class::Cursor::Cached" uses memcached for its own > backend. > http://search.cpan.org/~rkitover/Catalyst-Model-DBIC-Schema-0.48/lib/Catalyst/TraitFor/Model/DBIC/Schema/Caching.pm The advent article shows the configuration at the end: <Model::MyAppDB> schema_class MyApp::Schema <connect_info> (your connect_info) cursor_class DBIx::Class::Cursor::Cached traits Caching </connect_info> </Model::MyAppDB> And before that it shows the Catalyst cache setup with Memcached. -- Bill Moseley [email protected]
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
