Ticket #10252 (assigned)
Create a caching helper
Reported by: | MarcusNoble | Owned by: | Lottie Greenwood |
---|---|---|---|
Priority: | trivial | Milestone: | Release 3.5 |
Component: | Tools | Keywords: | AUTOREDUCTION |
Cc: | doucetm@…, tom.griffin@…, nick.draper@…, anders.markvardsen@… | Blocked By: | |
Blocking: | Tester: |
Description (last modified by MarcusNoble) (diff)
To prevent hammering ICAT too often with the same query (if a user is associated with an instrument etc.) it would be best if it could be stored in some sort of cache that expires after, say, 1 hour.
The cache should be able to store something similar to:
{ "user" : 123, "instruments" : ["ins1", "ins2"], "last_checked" : "2014-01-01 12:20" }
The cache should intercept the call to the ICAT helper and only proceed through if the cached values are too old or not found.
Update: Not sure yet if this is needed or not. Will reassess once page logic is in place.
Change History
comment:2 Changed 6 years ago by MarcusNoble
- Priority changed from minor to trivial
- Description modified (diff)
- Blocking 10147, 10242 removed
comment:3 Changed 6 years ago by MarcusNoble
- Milestone changed from Release 3.3 to Release 3.4
Pushing this back a release as I don't actually think it would be needed right away.
Leaving open as it is something that should be assessed after release.
Note: See
TracTickets for help on using
tickets.