Open VSX does a lot of internal caching already, however when putting a CDN in front of the application the application needs a way to instruct the CDN provider to purge relevant caches i.e. when a new extension version is published.
This would allow to do even more aggressive caching, e.g. the /vscode/gallery/<namespace>/<extension>/latest endpoint
Right now, endpoints that potentially return dynamic data have explicit cache control headers no-cache to prevent that stale data is returned.
Open VSX does a lot of internal caching already, however when putting a CDN in front of the application the application needs a way to instruct the CDN provider to purge relevant caches i.e. when a new extension version is published.
This would allow to do even more aggressive caching, e.g. the
/vscode/gallery/<namespace>/<extension>/latestendpointRight now, endpoints that potentially return dynamic data have explicit cache control headers
no-cacheto prevent that stale data is returned.