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

tahoe-lafs trac at tahoe-lafs.org
Thu Mar 7 17:38:59 UTC 2013


#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 ClashTheBunny):

 Rooted path seems to be the correct behavior that we would want to use for
 a programmatic interface.  The only reason to not require the rooted path
 would be to protect humans from another DIRCAP or a copy paste error.
 Because we're not trying to protect humans from this, there was agreement
 on the weekly dev chat that this is the technically correct approach.

 We made sure that the WUI does not display or use a move button in 1.9.x,
 so there are no supported WUI's out there that would be broken.  This
 means that there shouldn't be anybody left in the cold because of a change
 to this API.

 My one thing that I think I understand but want to explicitly state is:

 * If "NEWROOTEDPATH" exists and is a directory, it is considered a
 destination directory where the file will be moved with the same name.
 * If "NEWROOTEDPATH" exists and is a file, it is an exception and should
 be raised.
 * If "NEWROOTEDPATH" doesn't exist, but the path above it exists, it's
 considered the destination with a (possibly new) name.
 * If the path above "NEWROOTEDPATH" doesn't exist, it is an exception and
 should be raised.
 * If "NEWROOTEDPATH" isn't a rooted path, an exception is raised.  This
 case shall be shielded against for users of the WUI.  The WUI will
 probably default to appending the current DIRCAP.

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


More information about the tahoe-lafs-trac-stream mailing list