You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 26, 2025. It is now read-only.
This API might mesh better with multipart file uploads. Each ByteBuffer written can be mapped to an UploadPartRequest. Closing the channel can complete the upload, and the CompleteMultipartUploadResult returned from the S3 API can be used to cache file attribute information for the newly uploaded file.
Similarly, asynchronous downloads can be supported here, though I'm not sure on the corresponding APIs in S3.
The text was updated successfully, but these errors were encountered:
I had another thought: supporting GatheringByteChannel could also be used to parallelize the upload into chunks as well. This could make it simpler to use with APIs like ByteBuf in Netty.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This API might mesh better with multipart file uploads. Each ByteBuffer written can be mapped to an UploadPartRequest. Closing the channel can complete the upload, and the CompleteMultipartUploadResult returned from the S3 API can be used to cache file attribute information for the newly uploaded file.
Similarly, asynchronous downloads can be supported here, though I'm not sure on the corresponding APIs in S3.
The text was updated successfully, but these errors were encountered: