tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

"lafs" is more the protocol, "tahoe" is more the Python implementation 

[Imported from Trac: page NewCapDesign, version 30]
zooko 2013-09-11 06:32:25 +00:00
parent 206a1f693c
commit ccb2b71e42
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
NewCapDesign.md

@ -22,8 +22,8 @@ Ticket #432 was the starting point: it contained a list of features.
Kevin Reid points out that the Tahoe calls URIs are not actually URIs (in the
established sense). To make them real, we need to:
* make them start with `x-tahoe:` or `tahoe:` (or `lafs:`),
register `tahoe:` with IANA (#418) (#683)
* make them start with `x-lafs:` or `lafs:`,
register `lafs:` with IANA (#418) (#683)
* understand how URI/URL/URNs are built, decide about hierarchical segments
vs non-hierarchical segments. What's magical about a leading double-slash?
Do we need one?