[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:  assigned
     Priority:  major          |  Milestone:  1.10.0
    Component:  code-          |    Version:  1.9.1
  frontend-web                 |   Keywords:  forward-compatibility blocker
   Resolution:                 |
Launchpad Bug:                 |
-------------------------------+-------------------------------------------

Comment (by zooko):

 Replying to [comment:14 davidsarah]:
 > Actually, if we allow rooted paths, is it any longer necessary to have
 distinct parameters? A relative path and a rooted path can be
 distinguished exactly as they are by the CLI.

 Well, here is the form that uses a rooted path:

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

 The only use of the other form -- {{{POST
 /uri/$DIRCAP?t=move&from_name=OLD&to_dirname=SUBDIRNAME}}} would be to
 more succinctly express when you want the "to_dirname" to be relative to
 {{{$DIRCAP}}} instead of relative to a (different) root. So, I guess it is
 a tiny optimization and not worth the added complexity of API, IMO.

 So I think D-S is right, and a single API ({{{POST
 /uri/$DIRCAP?t=move&from_name=OLD&to=NEWROOTEDPATH}}}) is sufficient.

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