I was thinking about a major overhaul of the connection algorithm. Redis is improving quickly and more and more connection options are made available at each release. Both redis_cache and redis_sessions should be able to work on a "redis-like" connection object. In that rewrite I'd add this "flag" too. File a bug anyway on github so it gets tracked
On Wednesday, May 6, 2015 at 4:15:44 PM UTC+2, Jose C wrote: > > Hmm, I see your point and use case. But... ;) given that there are > references in the manual (and probably in reality the majority of use > cases) to caching views, or db queries, etc. how about then, as an > enhancement, to add an init flag to cache.redis along the lines of > `die_if_server_unavailable = True` to force a halt with the traceback. Or > else if set to False, fail silently and gracefully (key didn't exist > behaviour, re-execute function) and let the system keep running? > Obviously the flag name itself is up for debate. > > Would this not provide the best of both worlds and max flexibility? If > you (as the cache.redis creator) agree I'll take a stab at adding that > functionality to redis_cache.py and issue a PR. > > > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
