[tahoe-lafs-trac-stream] [tahoe-lafs] #1732: consider changes to webapi "Move" API before release

[tahoe-lafs]

#1732: consider changes to webapi "Move" API before release
-------------------------------+-------------------------------------------
     Reporter:  warner         |      Owner:  warner
         Type:  enhancement    |     Status:  new
     Priority:  major          |  Milestone:  1.10.0
    Component:  code-          |    Version:  1.9.1
  frontend-web                 |   Keywords:  forward-compatibility blocker
   Resolution:                 |
Launchpad Bug:                 |
-------------------------------+-------------------------------------------
Changes (by zooko):

 * status:  assigned => new


Comment:

 Thanks a lot for the review, !ClashTheBunny! I think your 5-point rules
 for handling this API call are right. Brian: does that look like a good
 API to you? Reassigning this ticket to Brian.

 One more question, too: I earlier, in comment:16, wrote

 {{{POST /uri/$DIRCAP?t=move&from_name=OLD&to=NEWROOTEDPATH}}}

 Should it actually be:

 {{{POST /uri/$ROOTEDPATH_TO_DIR?t=move&from_name=OLD&to=NEWROOTEDPATH}}}

 ? That is: does the caller have to supply the actual dircap of the
 original (source) directory, or can they use a rooted path to that
 directory?

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1732#comment:18>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage