Comment 4 for bug 1022614
Revision history for this message
| Maru Newby (maru) wrote Re: Memcache token backend does not expire tokens | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I've submitted a doc patch, but after consideration I would like to see the code change go in (if not now, in the future). auth_token is already performing explicit expiry checks rather than relying on implicit memcache expiry, and it would seem to make sense that the token backend rely on implicit expiry as well.
The complication is that anybody using the memcache token backend will have to bounce their memcache host(s) before upgrading to the token backend updated to use explicit expiry.
Joe: Thoughts? I suppose the doc change can go in for Folsom and the code change can follow eventually.