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

Review EOS TUS implementation and understand interplay with tusd lib interfaces #703

Open
labkode opened this issue Apr 30, 2020 · 1 comment

Comments

@labkode
Copy link
Member

labkode commented Apr 30, 2020

No description provided.

@ishank011
Copy link
Contributor

@butonic @labkode the way in which we were handling tus uploads was inefficient. Like you mentioned here, owncloud/ocis#997 (comment), even in the tus workflow, we were assembling all the chunks locally on the storageprovider machine and then copying the assembled file to EOS. This is also the way we handle v1 chunking which isn't ideal either.

EOS now has support for handling HTTP requests directly and the logic for combining the chunks, which I'm working on connecting now. Once we have that, we could directly forward the requests, making it a much better approach. So we could enable TUS again once that is done.

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

2 participants