I guess the remaining question to address is : close() It looks like it was added to appease an issue with memcached, which may or may not still be an issue [comments in tickets suggest it was a design decision by the memcached authors].
Thinking as I type... it wouldn't hurt, also, to allow a cache backend to provide an interface to a connection pool, so the manager can play friendly with it. If it doesn't have one, fall back to an instance-per-thread... this would require still hooking request complete, but not so much for "close" as "release". -- Curtis On 19 September 2013 01:33, Florian Apolloner <f.apollo...@gmail.com> wrote: > Hi, > > > On Wednesday, September 18, 2013 1:29:25 PM UTC+2, Curtis Maloney wrote: >> >> 1) Can we share "ad-hoc" caches -- that is, ones created by passing more >> than just the CACHES alias. >> > Imo no, you probably have a good reason if you create ad-hoc ones > >> 2) What to do about django.core.cache.cache ? >> > Has to stay for now, same as django.db.connection > > >> A separate approach is to introduce a new API to provide access to the >> shared, pre-configured caches, and retain get_cache for the old, ad-hoc, >> non-shared caches. >> > I think it would be sensible if that API would mimic django.db.connections > > Florian. > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
