PoC with response and API caching #372
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lwesterhof
force-pushed
the
portal-caching
branch
12 times, most recently
from
42111c9
to
00d8cbc
Compare
lwesterhof
force-pushed
the
portal-caching
branch
from
00d8cbc
to
0adb8ed
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds caching for Flask responses to avoid re-rendering templates, improving performance. It introduces API caching for a limited set of endpoints with defined timeouts.
Additionally, some API calls have been moved to the client side to leverage the template cache, further enhancing efficiency. Certain API calls will trigger cache clearing to ensure users receive up-to-date information.