Re: memcached-based-cache - timeout=0 does not work as intended by memcached

On Tue, Jul 27, 2010 at 4:04 PM, SmileyChris 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

Re: memcached-based-cache - timeout=0 does not work as intended by memcached

On Jul 27, 9:22 pm, Carl Meyer wrote: > The common thread, of course, is making it possible to write reusable > caching code without special-casing particular backends. I agree with Carl. We have an abstracted api - having a property with different meanings for different backends makes things a l

Re: memcached-based-cache - timeout=0 does not work as intended by memcached

On Jul 26, 10:02 am, Tobias McNulty wrote: > If such reusable code needs to cache things forever, which sounds perfectly > reasonable to me, I'd still rather not co-opt "0" to mean "forever" in all > cases.  Each backend that supports caching with no timeout could easily > offer a class attribut

Re: memcached-based-cache - timeout=0 does not work as intended by memcached

On Sat, Jul 24, 2010 at 4:07 PM, Carl Meyer wrote: > It's not obvious to me why .extra or .raw are the appropriate analogy > here, instead of the rest of the ORM API, which does attempt to > present the same semantics regardless of backend. > The issue is about values passed, not about semantics

Re: memcached-based-cache - timeout=0 does not work as intended by memcached

On Jul 23, 12:45 pm, Jacob Kaplan-Moss wrote: > On Fri, Jul 23, 2010 at 8:17 AM, Tobias McNulty > wrote: > > The only concern in that ticket seems to be that 0 means different things > > for different cache backends. > > There may have been some effort towards making them all behave the same w

Re: memcached-based-cache - timeout=0 does not work as intended by memcached

On Fri, Jul 23, 2010 at 8:17 AM, Tobias McNulty wrote: > The only concern in that ticket seems to be that 0 means different things > for different cache backends. > There may have been some effort towards making them all behave the same when > 0 is passed. > Personally I prefer the approach of not

Re: memcached-based-cache - timeout=0 does not work as intended by memcached

The only concern in that ticket seems to be that 0 means different things for different cache backends. There may have been some effort towards making them all behave the same when 0 is passed. Personally I prefer the approach of not messing with the value at all, and passing it straight to the c

Re: memcached-based-cache - timeout=0 does not work as intended by memcached

I thought this was familiar too: Is this the ticket you were thinking of? It seems to have been reopened. Cheers, Will Hardy -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this grou

Re: memcached-based-cache - timeout=0 does not work as intended by memcached

On Thu, Jul 22, 2010 at 10:43 AM, Alex Gaynor wrote: > On Wed, Jul 21, 2010 at 9:41 PM, Russell Keith-Magee > wrote: >> On Fri, Jul 16, 2010 at 6:54 PM, Carsten Reimer >> wrote: >>> Hello, >>> >>> I am not quite sure if this is the right mailinglist but as long as my >>> remarks are about a core

Re: memcached-based-cache - timeout=0 does not work as intended by memcached

On Wed, Jul 21, 2010 at 9:41 PM, Russell Keith-Magee wrote: > On Fri, Jul 16, 2010 at 6:54 PM, Carsten Reimer > wrote: >> Hello, >> >> I am not quite sure if this is the right mailinglist but as long as my >> remarks are about a core-component of django I hopefully chose the right >> list. >> >>

Re: memcached-based-cache - timeout=0 does not work as intended by memcached

On Fri, Jul 16, 2010 at 6:54 PM, Carsten Reimer wrote: > Hello, > > I am not quite sure if this is the right mailinglist but as long as my > remarks are about a core-component of django I hopefully chose the right > list. > > Dealing with cache-stuff in Django I realized that it seems to be imposs

Re: memcached-based-cache - timeout=0 does not work as intended by memcached

+1 2010/7/16 Tobias McNulty : > +1 > > Sent from my mobile device. > > On Jul 16, 2010 6:54 AM, "Carsten Reimer" > wrote: > > Hello, > > I am not quite sure if this is the right mailinglist but as long as my > remarks are about a core-component of django I hopefully chose the right > list. > > De

Re: memcached-based-cache - timeout=0 does not work as intended by memcached

+1 Sent from my mobile device. On Jul 16, 2010 6:54 AM, "Carsten Reimer" wrote: Hello, I am not quite sure if this is the right mailinglist but as long as my remarks are about a core-component of django I hopefully chose the right list. Dealing with cache-stuff in Django I realized that it se

memcached-based-cache - timeout=0 does not work as intended by memcached

Hello, I am not quite sure if this is the right mailinglist but as long as my remarks are about a core-component of django I hopefully chose the right list. Dealing with cache-stuff in Django I realized that it seems to be impossible to use a timeout=0 (which in terms of memcached meant that