[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:                 |
-------------------------------+-------------------------------------------

Comment (by davidsarah):

 I can think of two arguments for the second alternative:

 a) Consistency with {{{?t=rename}}}.

 b) The object modified by the POST is {{{$DIRCAP/[SUBDIRS../]}}}.
 {{{$DIRCAP/[SUBDIRS../]OLD}}} is not modified (unless it happens to be
 aliased to the source or destination directory).

 a) is not a strong argument; I would prefer conciseness over consistency
 with {{{?t=rename}}}.

 b) is a stronger argument, although the operation also modifies the
 destination directory which is not the object of the request. Still, I
 suppose this does mean that the second alternative is more consistent with
 REST, so I'm -0 on switching to the first alternative.

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