-
Notifications
You must be signed in to change notification settings - Fork 26
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
Improved TUS support #88
Comments
Resuming is supported but just not enabled by default. See https://github.com/tus/tus-js-client/blob/32b3544b7f04601d1d51aaa1eed12921f0a685ec/docs/api.md#urlstorage :) |
Sorry, I meant that in the version of tus-js-client that the current node-sdk version is using, resume was not supported. But I upgraded to latest tus-js-client verdion in my PR, and indeed now it’s just a matter of implementing the storage support :) I’m just not sure if resuming is something people would normally need in the node transloadit client. |
We normally do not what to implement resuming in the way a |
Oh, that's great to hear, thanks! |
Now that tusd supports uploading unknown length streams Fixes #88 - Pull out sendTusRequest into sepearte module so it can be mocked - Add argument chunkSize (defaults to 5MB only for unknown length streams, Infinity for file streams, same as tus-js-client) - Emit deprecation warning when isResumable is set to false
* Use tus for all uploads Now that tusd supports uploading unknown length streams Fixes #88 - Pull out sendTusRequest into sepearte module so it can be mocked - Add argument chunkSize (defaults to 5MB only for unknown length streams, Infinity for file streams, same as tus-js-client) - Emit deprecation warning when isResumable is set to false * upgrade tus-js-client to v2.3.0 * limit tus upload concurrency (default 10) * increase tus default chunk size to 50MB
Seems like resuming is supported by default in the new tus-js-client
The text was updated successfully, but these errors were encountered: