errata corrige on BTW2: on redis, time_expire=None results in key stored at most one day. you can always do time_expire=30*24*60*60 for 30days worth.
things_to_know: only cache.disk and cache.ram can effectively cache a value indefinitely and enable that strange behaviour of retrieving the previously cached element - that you marked to expire after 5 seconds - one day later. Web2py's cache API is effectively incompatible with any high-performance caching system, unless the user calls upon himself the burden of clearing the cache regularly (which is never the case because cache invalidation is one of the hardest things to master). Both memcache and redis take a more strict behaviour, i.e. the value will effectively expire at the time it was set on the first time. So, you can only fetch a cached value one day later if you originally marked it as expiring one day later. Redis allows a leeway of 120 seconds to accomodate the 90% of the behavioural usecases of cache.ram and cache.disk. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
