[tahoe-lafs-trac-stream] [tahoe-lafs] #2040: mutable files: expose test-and-set operations to HTTP clients

tahoe-lafs trac at tahoe-lafs.org
Sat Jul 27 01:32:48 UTC 2013


#2040: mutable files: expose test-and-set operations to HTTP clients
-------------------------+-------------------------------------------------
     Reporter:  daira    |      Owner:  daira
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  undecided
    Component:  code-    |    Version:  1.10.0
  mutable                |   Keywords:  mutable versioning test-and-set
   Resolution:           |  webapi wui
Launchpad Bug:           |
-------------------------+-------------------------------------------------
Changes (by daira):

 * keywords:   => mutable versioning test-and-set webapi wui
 * component:  unknown => code-mutable


Old description:

> From ticket:413#comment:2
> * Dirnode operations could accept a new argument which provides test-and-
> set semantics, perhaps "if-old-version-is=XYZ". The webapi protocol would
> only apply the requested changes if the "current best version" is also
> described as XYZ
> * The human-oriented "wui" could acquire if-old-version-is= arguments on
> all the buttons it provides. If the directory has been changed between
> the time the directory page was rendered and the time someone clicks a
> button, the operation would be rejected with a note encouraging the user
> to reload the page (and thus get the latest version).
>
> Both mutable files and directories could have a control like this.

New description:

 Split from ticket:413#comment:2
 * Dirnode operations could accept a new argument which provides test-and-
 set semantics, perhaps "if-old-version-is=XYZ". The webapi protocol would
 only apply the requested changes if the "current best version" is also
 described as XYZ
 * The human-oriented "wui" could acquire if-old-version-is= arguments on
 all the buttons it provides. If the directory has been changed between the
 time the directory page was rendered and the time someone clicks a button,
 the operation would be rejected with a note encouraging the user to reload
 the page (and thus get the latest version).

 Both mutable files and directories could have a control like this.

--

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


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