[GitHub] [couchdb] nickva commented on issue #2331: Expiring cache

[GitBox <gi...@apache.org>]

nickva commented on issue #2331: Expiring cache
URL: https://github.com/apache/couchdb/pull/2331#issuecomment-562275046
 
 
   @jaydoane I was thinking it would be like having N expiring caches, one for each application that needs it. Each would have its own timeouts, etc. Presumably the expiring cache for OAuth2 vs some other auth mechanism could need different expiry and stale timeouts. The model would then look like:
   
   ```
   (?EXPIRING_CACHE, Name, ?PK, Key) := (Val, StaleTS, ExpireTS)
   (?EXPIRING_CACHE, Name, ?EXP, ExpireTS, Key) := ()
   ```
   
   So there would be one for OAuth2 with something like `Name = oauth2_xcache`. If there another auth library application it would have `Name = otherlib_xcache`. Each application would then be in charge of starting its own expiry cache child in its supervisor, cleaning up stale entries, updating entries, etc.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services