Protocol specifiers are ambiguous?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go
- Domain
- networking
Research direction
Start with protocols.csv and the multiaddr examples in the issue, especially the unix path and nested wss/http forms. Determine how protocol boundaries and filesystem paths are specified and parsed. Done means the specification resolves these ambiguities without relying on unstated context.
Written by the indexing model from the issue text.
Description
If you use Unix file paths and delimiters, it seems like it would be really easy to make things ambiguous.
First off, I don't see a "file" protocol type, is this the the unix protocol type listed in protocols.csv?
If so, what happens if I make a file path /home/icefox/tcp/127.0.0.1/foo and try to represent it as a multiaddr path?
/unix/home/icefox/tcp/127.0.0.1/foo
Okay, that's a little artificial, and you could specify that you can disambiguate from context; a unix protocol address cannot contain a tcp protocol subaddress. Though that seems to defeat the purpose; things stop being self-describing and become context-dependent. (And on Plan9 you certainly can do TCP via the filesystem.)
Okay, what about a more concrete example using already defined protocols:
/wss/example.com/http/example.com
Is this accessing the websockets endpoint wss://example.com/http/example.com, or is it trying to nest the HTTP protocol inside the websockets endpoint wss://example.com/ ?
- Dominant language
- Go
- Stars
- 482
- Forks
- 87
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from multiformats/multiaddr
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
multiformats/multiaddr#181 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
multiformats/multiaddr#178 · 4 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
multiformats/multiaddr#168 ·
-
Multiaddr URI scheme Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
multiformats/multiaddr#165 · 2 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
multiformats/multiaddr#156 · 1 reaction ·
All issues in multiformats/multiaddr
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·