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

Add more owncloud/nextcloud client headers #3552

Merged
merged 1 commit into from
Sep 4, 2021

Conversation

mnutt
Copy link
Contributor

@mnutt mnutt commented Aug 17, 2021

Adds some additional ownCloud/NextCloud client headers relating to mnutt/davros#114.

The new headers:

  • oc-checksum - a hash (typically SHA1) of the entire file. After all chunks have been uploaded, davros should be checking this to ensure that it uploaded correctly, otherwise we may end up saving a corrupted file. [this header has been around for a while, I should have been doing this all along]
  • oc-chunk-offset - part of a new chunking scheme. Right now the legacy chunking scheme relies on all chunks being the same size in order to calculate the offset (number * chunkSize); this header would allow the client to vary the chunk size based on timing/bandwidth.
  • oc-lazyops - I'm unlikely to implement this soon, but it would be a way for the client to signal "I don't want to wait for a response". The server would then hypothetically respond with a location where the client could poll for progress updates.

Adds some additional ownCloud/NextCloud client headers relating to mnutt/davros#114.

The new headers:
* `oc-checksum` - a hash (typically `SHA1`) of the entire file. After all chunks have been uploaded, davros should be checking this to ensure that it uploaded correctly, otherwise we may end up saving a corrupted file. [this header has been around for a while, I should have been doing this all along]
* `oc-chunk-offset` - part of a new chunking scheme. Right now the legacy chunking scheme relies on all chunks being the same size in order to calculate the offset (number * chunkSize); this header would allow the client to vary the chunk size based on timing/bandwidth.
* `oc-lazyops` - I'm unlikely to implement this soon, but it would be a way for the client to signal "I don't want to wait for a response". The server would then hypothetically respond with a location where the client could poll for progress updates.
@ocdtrekkie ocdtrekkie added app-platform App/Sandstorm integration features ready-for-review We think this is ready for review labels Aug 17, 2021
@kentonv kentonv merged commit 7267c05 into sandstorm-io:master Sep 4, 2021
@ocdtrekkie ocdtrekkie removed the ready-for-review We think this is ready for review label Sep 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app-platform App/Sandstorm integration features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants