You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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
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.
The text was updated successfully, but these errors were encountered: