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

Optionally store a local copy of (generated) files (caching) #70

Open
benoitbryon opened this issue Nov 26, 2013 · 0 comments
Open

Optionally store a local copy of (generated) files (caching) #70

benoitbryon opened this issue Nov 26, 2013 · 0 comments

Comments

@benoitbryon
Copy link
Collaborator

Currently, optimizations are not available for every backend, and virtual files cannot be streamed by reverse proxies.
Moreover, if someone requests the same virtual file twice, contents must be generated again from scratch.
One solution would be to have a cache for generated files. Or for any file, including HTTPFile or remote StorageFile.
The cache would make it possible to avoid re-generation of files.
It also would make it possible to resume a download (see #67) for virtual files.
If the cache is local, then it would allow Apache and Lighttpd to stream remote files (they are currently limited to local files).

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