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

determine if client can use cached version of packages list "available applications" #54

Open
line-o opened this issue Feb 15, 2021 · 0 comments

Comments

@line-o
Copy link
Member

line-o commented Feb 15, 2021

Is your feature request related to a problem? Please describe.

This would speed up most requests as the last loaded list is the current one most of the time and also release resources on the server where the public repo is installed.

Describe the solution you'd like

Whenever the list of available packages is queried the server sends a header that will enable to easily determine if that specific listing has changed on subsequent requests.

That could be an eTag or last-modified header.

Describe alternatives you've considered

Leaving it as it is. Every request will rebuild the list of compatible and available packages.

Additional context

This will only have effect when an updated package-service is able to handle responses with status code 304, not modified.

@line-o line-o changed the title allow clients to use a cached version of apps.xml "available applications" in package manager determine if client can use cached version of apps.xml "available applications" Feb 15, 2021
@line-o line-o changed the title determine if client can use cached version of apps.xml "available applications" determine if client can use cached version of packages list "available applications" Feb 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant