Opened at 2021-09-01T15:10:25Z
Last modified at 2022-11-17T17:19:59Z
#3783 closed task
IServer has a bunch of Foolscap-specific assumptions that need fixing — at Version 1
| Reported by: | itamarst | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | HTTP Storage Protocol |
| Component: | unknown | Version: | n/a |
| Keywords: | Cc: | itamarst | |
| Launchpad Bug: |
Description (last modified by itamarst)
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
Change History (1)
comment:1 Changed at 2021-09-01T15:10:59Z by itamarst
- Description modified (diff)
Note: See
TracTickets for help on using
tickets.
