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.

Sign up for GitHub

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

Jump to bottom

TUS client-ready: expose etag/fileid at the end of upload #78

Closed
1 of 2 tasks
exalate-issue-sync bot opened this issue Jun 8, 2020 · 3 comments
Closed
1 of 2 tasks

TUS client-ready: expose etag/fileid at the end of upload #78

exalate-issue-sync bot opened this issue Jun 8, 2020 · 3 comments
Assignees
@PVince81
Labels
Exalated This issue is under sync OCIS-Sprint-12 p3-medium story User Story

Comments

@exalate-issue-sync
Copy link

exalate-issue-sync bot commented Jun 8, 2020 •
edited by PVince81
Loading

owncloud/ocis#216

Blocker for the client DEV

Tasks

  • Adjusting the creation-with-upload response
  • Return at the end of PATCH

Estimate

M / M
@exalate-issue-sync exalate-issue-sync bot added Exalated This issue is under sync p3-medium story User Story labels Jun 8, 2020
@exalate-issue-sync
Copy link
Author

Remote key is https://jira.owncloud.com/browse/OCIS-102

@PVince81 PVince81 self-assigned this Jun 8, 2020
@PVince81
Copy link

implemented the "creation-with-upload" case in cs3org/reva#813

as discussed before, we will not address the PATCH case: owncloud/ocis#216 (comment)

@exalate-issue-sync
Copy link
Author

Vincent Petry commented: Returning the etag and fileid at the end of a chunked upload will be reconsidered once we address asynchronous assembly and workflow: https://jira.owncloud.com/browse/OCIS-142

@PVince81 PVince81 mentioned this issue Sep 3, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@PVince81 PVince81

Labels
Exalated This issue is under sync OCIS-Sprint-12 p3-medium story User Story
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@PVince81