Skip to content
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

Render function cache within HTTP pipeline #3

Open
tokrug opened this issue Jan 26, 2021 · 0 comments
Open

Render function cache within HTTP pipeline #3

tokrug opened this issue Jan 26, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@tokrug
Copy link
Collaborator

tokrug commented Jan 26, 2021

As of now there is only one type of cache available which checks if the original HTML for a given path has changed or not. If it did then the new HTML is transformed into a render function and stored for future requests.

While it does save some time spent on parsing the HTML which does not change most of the time, an HTTP request is still executed on every pipeline call.

Introduce a new cache specific to the HTTP pipeline that would use headers and other HTTP data in addition to the request page path as the cache key.

@tokrug tokrug added the enhancement New feature or request label Jan 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant