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

Consider a better method to invalidate remote config URL cache #774

Open
g-plane opened this issue Nov 2, 2023 · 0 comments
Open

Consider a better method to invalidate remote config URL cache #774

g-plane opened this issue Nov 2, 2023 · 0 comments

Comments

@g-plane
Copy link
Contributor

g-plane commented Nov 2, 2023

When extending a remote config with a URL, current implementation is hashing the URL string and using hash as cache key. This can be a trouble because when remote config updated, there's no good way to invalidate the cache. Putting version in URL isn't convenient because someone must remember or check the latest URL.

Current implementation:

async fn resolve_url<TEnvironment: Environment>(url: &Url, environment: &TEnvironment) -> Result<ResolvedPath> {

Is there a better way to invalidate the cache without updating the URL manually?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant