tahoe-lafs/tahoe-lafs
tahoe-lafs/tahoe-lafs
2
0
Fork 0
Code Issues Pull Requests 23 Packages Projects Releases 1 Wiki Activity

Updates based on changing specs.

Browse Source
This commit is contained in:
Itamar Turner-Trauring 2023-07-25 15:32:14 -04:00
parent 46d10a6281
commit 7bac6996d1
1 changed files with 2 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/proposed/http-storage-node-protocol.rst
View File

@ -279,7 +279,7 @@ Such an announcement will resemble this::
{ {
"anonymous-storage-FURL": "pb://...", # The old key "anonymous-storage-FURL": "pb://...", # The old key
"gbs-anonymous-storage-url": "pb://...#v=1" # The new key "anonymous-storage-NURLs": ["pb://...#v=1"] # The new keys
} }
The transition process will proceed in three stages: The transition process will proceed in three stages:
@ -320,12 +320,7 @@ The follow sequence of events is likely:
Ideally, Ideally,
the client would not rely on an update from the introducer to give it the GBS NURL for the updated storage server. the client would not rely on an update from the introducer to give it the GBS NURL for the updated storage server.
Therefore, In practice, we have decided not to implement this functionality.
when an updated client connects to a storage server using Foolscap,
it should request the server's version information.
If this information indicates that GBS is supported then the client should cache this GBS information.
On subsequent connection attempts,
it should make use of this GBS information.
Server Details Server Details
-------------- --------------