We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Resumption is likely to become a necessity for very large blobs in many use cases. To start off discussion, what about:
Where resume_opts are the options specifically needed to identify what and how to resume a write?
resume_opts
I could see something similar for resuming from a read stream, though maybe range requests are the right way to handle that, I'm not sure.
The text was updated successfully, but these errors were encountered:
for inspiration: https://cloud.google.com/storage/docs/concepts-techniques#resumable
Sorry, something went wrong.
and for reference, I implemented this in s3-upload-stream: nathanpeck/s3-upload-stream#25
s3-upload-stream
No branches or pull requests
Resumption is likely to become a necessity for very large blobs in many use cases. To start off discussion, what about:
store.resumeWriteStream(resume_opts, opts, cb)
Where
resume_opts
are the options specifically needed to identify what and how to resume a write?I could see something similar for resuming from a read stream, though maybe range requests are the right way to handle that, I'm not sure.
The text was updated successfully, but these errors were encountered: