POST /uri?t=upload should give Upload Results consistently (even mutable) #1560

Open
opened 2011-10-13 15:28:05 +00:00 by warner · 0 comments

The docs in source:docs/frontends/webapi.rst currently claim (in section 6.5, "Browser Operations" > "Uploading a File", around line 1150) that doing a POST to /uri?t=upload will always "return an HTML page that describes the results of the upload. This page will contain information about which storage servers were used for the upload, how long each operation took, etc".

At present, we only actually do that for immutable uploads. When creating or modifying a mutable file, it just returns the filecap.

We should implement a PublishResults object, have mutable-file creation (and probably modification) populate it with a few useful items, and return it from .publish, then write a renderer for it.

The docs in source:docs/frontends/webapi.rst currently claim (in section 6.5, "Browser Operations" > "Uploading a File", around line 1150) that doing a POST to `/uri?t=upload` will always "return an HTML page that describes the results of the upload. This page will contain information about which storage servers were used for the upload, how long each operation took, etc". At present, we only actually do that for immutable uploads. When creating or modifying a mutable file, it just returns the filecap. We should implement a `PublishResults` object, have mutable-file creation (and probably modification) populate it with a few useful items, and return it from `.publish`, then write a renderer for it.
warner added the
code-frontend-web
minor
defect
1.9.0a2
labels 2011-10-13 15:28:05 +00:00
warner added this to the eventually milestone 2011-10-13 15:28:05 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1560
No description provided.