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

The web runtime should try to cache Runes where possible #376

Open
Michael-F-Bryan opened this issue Nov 5, 2021 · 0 comments
Open

The web runtime should try to cache Runes where possible #376

Michael-F-Bryan opened this issue Nov 5, 2021 · 0 comments
Labels
area - web-runtime A runtime that runs in the browser. category - performance Something that impacts runtime performance. effort - easy This should be pretty simple

Comments

@Michael-F-Bryan
Copy link
Contributor

As a convenience, the web runtime's builder() can accept the URL of a Rune. This is awesome because you don't have to call fetch() yourself, but can also be a massive pain when you need to download the same 50MB Rune from the internet every time you reload.

Inside Builder.build() we should use the browser's caching functionality to avoid re-downloading the same file every time.

@Ge-te and @binaryanthems, do you know what the best way to do this is?

@Michael-F-Bryan Michael-F-Bryan added category - performance Something that impacts runtime performance. effort - easy This should be pretty simple area - web-runtime A runtime that runs in the browser. labels Nov 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area - web-runtime A runtime that runs in the browser. category - performance Something that impacts runtime performance. effort - easy This should be pretty simple
Projects
None yet
Development

No branches or pull requests

1 participant