[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4017: WebUI: enhance "put" operations

[Tahoe-LAFS]

#4017: WebUI: enhance "put" operations
-------------------------+---------------------------
 Reporter:  meejah       |          Owner:
     Type:  enhancement  |         Status:  new
 Priority:  normal       |      Milestone:  undecided
Component:  unknown      |        Version:  n/a
 Keywords:               |  Launchpad Bug:
-------------------------+---------------------------
 Currently, the WebUI API for uploading a file (aka `tahoe put`) only
 returns when the file is uploaded to storage-servers.

 This makes sense: your file isn't "put" into Tahoe until that happens.
 However, it makes progress information hard because the fine-grained
 progress API indexes operations by "storage-index" which you only learn
 after the HTTP operation that `tahoe put` uses is completely finished.

 It's also not useful to show progress of the data-transfer: Tahoe accepts
 it quickly (usually this is via localhost) into a temporary area before
 doing erasure-encoding etc and uploading to storage-servers.

 One approach could be a "two-part" API where you initiate the operation
 (i.e send all the data to your local tahoe client) and receive a handle of
 some kind. If possible, this could be the storage-index.

 Then, a second API can be used to "wait for handle X to complete".
 Meantime, the existing progress information is used to determine the
 encoding and upload (to actual storage-servers) progress. (Note that this
 needs a storage-index currently).

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4017>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage