Bug #2726
References are cached with the verse ID (even though it is the same chapter)
Start date:
05/11/2020
Due date:
% Done:
100%
Associated revisions
Adding improved cache control
It not doesn't cache verses
It also can load a chapter and then add in the verse info
Reference #2726
Improving cache handling
Reference #2726
History
#1
Updated by Luke Murphey almost 4 years ago
Updated by - Target version changed from Plus_2 to 4.0
#2
Updated by Luke Murphey almost 4 years ago
Obs:
- The following changes when a verse to highlight is selected
- verse_to_highlight
- verse_not_found
- warnings
- title
- How do I determine what verse to highlight?
- Comes from get_division_and_verse
- What part of the API response is so slow?
- The rendering of the HTML is a big part
- How do I get the browser to cache to cache the responses?
- Cache the response manually, add in the verse data afterwards
- I could have the system store only the chapter part long-term
- The cache system could check for existence of a match for the URL. If it finds one, it can assume it was for a chapter only and just return what it got (and not bother with the verse only functionality).
- The cache key ought to be the URL portion of the work (work and divisions)
#3
Updated by Luke Murphey almost 4 years ago
I think I need to not cache response with leftovers. This is currently ignored.
#4
Updated by Luke Murphey almost 4 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100