Skip to content

Support streaming object upload without passing file size (Content-Length) #2

@clue

Description

@clue

The putObject() API as implemented in #1 requires a Content-Length request header (https://developers.digitalocean.com/documentation/spaces/#object), the request will be rejected when this request header is not present.

As an alternative, we might take advantage of multipart uploads (https://developers.digitalocean.com/documentation/spaces/#begin-multi-part-upload) by buffering some data (minimum chunk size >5MB) and then processing it like a "chunk" while buffering the next chunk. Implementation-wise this probably isn't trivial, but certainly doable.

Personally, my use cases are solved by explicitly passing in the file size as an additional argument, but this might still be interesting in the future.

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is needednew featureNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions