[tahoe-lafs-trac-stream] [tahoe-lafs] #413: mutable files: expose version info to HTTP clients?

[tahoe-lafs]

#413: mutable files: expose version info to HTTP clients?
-----------------------------------+-------------------------------
     Reporter:  warner             |      Owner:
         Type:  enhancement        |     Status:  new
     Priority:  major              |  Milestone:  eventually
    Component:  code-frontend-web  |    Version:  1.0.0
   Resolution:                     |   Keywords:  mutable integrity
Launchpad Bug:                     |
-----------------------------------+-------------------------------
Description changed by zooko:

Old description:

> in #328, we overhauled the internal API for mutable files, to make them
> safe to use for structured data that requires test-and-set semantics. But
> this is not currently exposed to the webapi: clients using HTTP can only
> blindly overwrite mutable files, making them unsuitable for carrying more
> structured data that must be manipulated outside the tahoe node.
>
> I'm not convinced that passing a servermap outside (and back into!) the
> tahoe node over HTTP is a good idea. Maybe passing a handle to one might
> be safe.

New description:

 in #328, we overhauled the internal API for mutable files, to make them
 safe to use for structured data that requires test-and-set semantics. But
 this is not currently exposed to the webapi: clients using HTTP can only
 blindly overwrite mutable files, making them unsuitable for carrying more
 structured data that must be manipulated outside the tahoe node.

 I'm not convinced that passing a servermap outside (and back into!) the
 tahoe node over HTTP is a good idea. Maybe passing a handle to one might
 be safe.

 If you like this ticket, you might also like #906.

--

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