3 Oct
2011
3 Oct
'11
12:41 p.m.
2011/10/3 Niels Larsen <niels@genomics.dk>:
If memcached is used as session engine, then session get and set will make a network request to whatever server is configured, I assume. Which is slower than first getting the entire session, then modifying it throughout the application, then saving it, as an after-template hook for example. But I do not see an operator to set an entire session? or is that a wrong-headed idea anyway?
So you want to cache your access to the cache engine? :) Well, not sure that's really worth the effort, at least semantically.