Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editions crossword cryptic and quick data #27604
Editions crossword cryptic and quick data #27604
Changes from 3 commits
eb1900e
d600162
115f994
f6b8b9a
cc8dd30
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why
CacheTime.Facia
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All of the other post requests in the DotcomRenderingService are using this cache time including for articles. Its confusingly named, maybe we can look at reviewing this separately.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think generally post requests for articles are using a different cache time based on their metadata:
frontend/common/app/renderers/DotcomRenderingService.scala
Line 215 in c7b403b
frontend/common/app/renderers/DotcomRenderingService.scala
Line 311 in c7b403b
with
CacheTime.Default
as the fallback:frontend/common/app/model/meta.scala
Line 326 in c7b403b
?
Post requests for fronts and tag pages are using
CacheTime.Facia
, but that's likely correct because they're examples of "facia" content. I agree that probably we should reviewgetMedia
,getImageContent
andgetGallery
's usage ofCacheTime.Facia
; have captured this in #27628.Given this, I don't think it's what we want to use here. Perhaps
CacheTime.Default
is the correct choice if we don't have a specific, different cache setting for these pages? @SiAdcock @arelra any thoughts?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. I didn't think about this much and just copied what was being done for similar use cases. What about 50 minutes surrogate and 5 minutes for client cache arbitrarily. This is a simple optimisation unlikely to effect users too much unless that are hitting crosswords in press reader at midnight