[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3783: IServer has a bunch of Foolscap-specific assumptions that need fixing

[Tahoe-LAFS]

#3783: IServer has a bunch of Foolscap-specific assumptions that need fixing
--------------------------+-----------------------------------
     Reporter:  itamarst  |      Owner:
         Type:  task      |     Status:  new
     Priority:  normal    |  Milestone:  HTTP Storage Protocol
    Component:  unknown   |    Version:  n/a
   Resolution:            |   Keywords:
Launchpad Bug:            |
--------------------------+-----------------------------------
Description changed by itamarst:

Old description:

> Do we need IServer, or is it really just NativeStorageServer and the
> interface can go away?
>
> More broadly there's some basic impedance mismatch between connection-
> oriented foolscap and request-oriented GBS. E.g. the webui wants to show
> users how many servers they're "connected to". There may be some test
> code that tries to wait until "enough" servers are "connected to".
>
> So step 1 is... investigate that and write up design. Or something

New description:

 Do we need IServer, or is it really just NativeStorageServer and the
 interface can go away?

 More broadly there's some basic impedance mismatch between connection-
 oriented foolscap and request-oriented GBS. E.g. the webui wants to show
 users how many servers they're "connected to". There may be some test code
 that tries to wait until "enough" servers are "connected to".

 The share placement algorithm (which servers to put a share on) wants to
 operate on a set of "connected" servers.

 So step 1 is... investigate that and write up design. Or something

--

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