Closed necrophonic closed 10 years ago
can't really merge this or we'd lose most of the performance gain in caching! we'd need some way to detect that the memcached connection has failed, and same applies to the other caching backends (though I'd have thought that would be handled internally by the cache client library anyway)
its likely to be an asynchronous issue with the memcached client library, can we replicate the problem using the redis backend?
Not currently required - issue raised #9 to address more permanently at a later date.
Attempt to address the issue of sessions "sticking" when used with MojoX::Security::Session.
This issue manifests when some requests (not reliably replicable) "stick" - the
get
call tomemcached
doesn't return and the mojolicious request times out. Subsequent calls then mostly just timeout.Creating a new instance of
Memcached::Client
each request doesn't suffer from the issue but feels wrong currently.