multistream-select

multistream-select copied to clipboard

multistream-select specification isn't very clear

2

Reading the spec I noticed that the code blocks in the beginning show a pseudo-wire protocol representation by just showing the contents of each message without explicitly showing the varint...

dhuseby

Upon navigating to the Multiformat protocols heading on the Multiformats homepage ([https://multiformats.io/#multiformat-protocols](url)), you will notice that multistream-select is not in that list.

sydbarrett74

String representation character encoding

3

Just a short question here: What is the character encoding of the protocol strings? I realize that the spec only talks about bytes, but implementations expose it as strings for...

ntninja

ls protocol format is unfriendly

4

I'm still not on board with the protocol here. It feels broken. Multistream select's primary operation is reading a length prefixed newline delimited string. Lets call this operation `readLpNd()`. Interacting...

whyrusleeping

idea: optimistic failure resets

4

I was thinking that nodes could optimistically select a protocol and then start immediately sending data. If the other side cannot handle the assumed protocol, they could respond with a...

whyrusleeping

Update Docs + API after the matchingFunc discussion. We discussed: - multistream takes in a tuple: `(multicodec-header, handlerFunc, matchingFunc)` - `handlerFunc` is called with the header - `matchingFunc` decides whether...

jbenet