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

 Replying to [comment:30 warner]:
 > Talking with zooko at pycon, we think the following might be best:
 >
 > {{{
 > POST
 /uri/$DIRCAP/[SUBDIRS../]?t=move&from_name=OLD&to_dir=$NEWDIRCAP/[NEWSUBDIRS../]&to_name=NEW[&replace=true|false
 |only-files]
 > }}}

 Ah yes, I see the consistency argument for that. In that case perhaps
 {{{to_name}}} should default to {{{from_name}}} after all.

 > Zooko's first spelling ({{{.../OLD?t=move&to=...NEW}}}) would be
 nice(r), but the webapi code uses twisted.web Resource traversal to find
 the dir/file object referenced by the URL, and to accomodate
 {{{.../OLD}}}) we'd need to change that code to remember the penultimate
 Resource (the directory), which would be a lot of work. (parsing {{{to=}}}
 is easier: we could just regexp off the last slash).

 That seems like a compelling argument. So the choice is now between
 comment:25 and comment:30.

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