You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -134,7 +158,6 @@ These path names happen to be resolvable -- not just in a "multicodec muxer(e.g
134
158
-[js-multistream](https://github.com/multiformats/js-multistream) - Implements multistream, which uses multicodec for stream negotiation
Copy file name to clipboardExpand all lines: multicodec-packed.md
-32Lines changed: 0 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,38 +50,6 @@ It is worth noting that multicodec-packed works very well in conjunction with [m
50
50
51
51
Multicodec-packed uses "protocol tables" to agree upon the mapping from one multicodec-packed code (a single varint). These tables map an `<mcp-code>` to a full [multicodec protocol path](./README.md#the-protocol-path). These tables can be application specific, though -- like [with](https://github.com/multiformats/multihash)[other](https://github.com/multiformats/multibase)[multiformats](https://github.com/multiformats/multiaddr) -- we will keep a globally agreed upon table with common protocols and formats.
52
52
53
-
### Standard mcp protocol table
54
-
55
-
This is the standard multicodec-packed protocol table.
56
-
57
-
**WARNING: WIP. this table is not ready for wide use.**
58
-
59
-
TODO:
60
-
-[ ] See if IANA has a ready-made table for us to use here. Even just a listing of the most popular formats would be good enough.
0 commit comments