On Tue, Jul 27, 2010 at 4:04 PM, SmileyChris <smileych...@gmail.com> wrote: > > I agree with Carl. > We have an abstracted api - having a property with different meanings > for different backends makes things a lot less pluggable.
Sure. Upon closer investigation, I think this is pretty much a non-issue. My only point is that all cache backends should receive whatever timeout they're passed, unmolested by Django. Given that all the backends, besides memcache, are implemented in the Django source, I see no reason why they couldn't be modified on a case by case basis to support a "cache forever" option, indicated by timeout=0, while leaving the common code intact and without really co-opting anything. Establishing this as a loose convention seems like a reasonable enough plan to me. I will say that the memcache issue seems more like a bug, while special-casing timeout=0 for all the other backends seems more like a feature (and one that may require a lot more discussion, code, and testing relative to the 1-line memcache fix). Cheers, Tobias -- Tobias McNulty Caktus Consulting Group, LLC P.O. Box 1454 Carrboro, NC 27510 USA: +1 (919) 951-0052 http://www.caktusgroup.com -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
