ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2024-12-20 05:28:04 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

a *few* words about this option at least

Browse Source
This commit is contained in:
Jean-Paul Calderone 2020-11-11 13:19:29 -05:00
parent 36ab26c718
commit 153ceb9ff4
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/proposed/http-introducer-internals.rst
View File

@ -179,3 +179,14 @@ x-ocap
`````` ``````
Or some other nice-looking brand new string. Or some other nice-looking brand new string.
This option has the least obvious semantics.
In inventing an entirely new scheme,
we have to invent all of its behavior.
This could be like the *pb* option but with a new name and no baggage from Foolscap.
As soon as we decide to make another protocol change then we're back in the same place as we are now.
The only difference is that the "HTTP Introducer" protocol would play the part Foolscap now plays.
For the purposes of migrating from Foolscap it has the same drawback as *pb+http*:
there are two URIs clients must be made aware of.