[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3779: Ensure IStorageServer using code doesn't have interactions that conflict with HTTP implementation

[Tahoe-LAFS]

#3779: Ensure IStorageServer using code doesn't have interactions that conflict
with HTTP implementation
----------------------+---------------------------------------
 Reporter:  itamarst  |          Owner:  itamarst
     Type:  task      |         Status:  new
 Priority:  normal    |      Milestone:  HTTP Storage Protocol
Component:  unknown   |        Version:  n/a
 Keywords:            |  Launchpad Bug:
----------------------+---------------------------------------
 On the assumption that we keep `IStorageServer` in place, and provide a
 HTTP implementation of the interface, current users of the interface need
 some updates.

 In particular, some parts of the code make unwarranted assumptions about
 interaction patterns, e.g. that if command A is run before command B then
 command A will be started before command B. With an HTTP client, these
 commands will be sent in parallel, not necessarily over the same TCP
 connection as Foolscap does, so this assumption won't always be true.

 For this particular example, the code would need to be modified so that B
 was only sent when a response is received from the A command, ensuring the
 required ordering.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3779>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage