mutable files: expose test-and-set operations to HTTP clients #2040

New Issue

tahoe-lafs · 2013-07-27T01:31:26Z

daira commented

2013-07-27 01:31:26 +00:00

Split from /tahoe-lafs/trac-2024-07-25/issues/5475#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.

Split from [/tahoe-lafs/trac-2024-07-25/issues/5475](/tahoe-lafs/trac-2024-07-25/issues/5475)#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.