-
Notifications
You must be signed in to change notification settings - Fork 93
feat: multistream-select #297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
||
[Multistream Select](https://github.com/multiformats/multistream-select) is | ||
a protocol for friendly protocol multiplexing that allows for the negotiation | ||
of a [multicodec](https://github.com/multiformats/multicodec) between two entities. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it a multicoded? It's just a string, isn't it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes.. thanks!
The header refers to the initial message sent by a peer to initiate the protocol | ||
negotiation process. This message includes the protocol ID, `/multistream/1.0.0.`, | ||
which indicates to the listening peer that a protocol negotiation process is about | ||
to take place. Upon receiving this header, the listening peer responds with their | ||
desired protocol header. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wouldn't put too much emphasis on the header. It's not terribly important. Just say: Every multistream message is prefixed with a header, /multistream/1.0.0
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Simplified
protocol information and select the protocols to use for the connection, including | ||
protocols for [security](../../secure-comm/overview.md) and | ||
[stream multiplexing](../../multiplex/overview.md) if necessary. The | ||
[protocol negotiation](../core-abstractions/connections#protocol-negotiation) | ||
and [upgrade process](../core-abstractions/connections#upgrading-connections) | ||
is explained further in the [connections document](../core-abstractions/connections.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be mentioned in the first paragraph:
libp2p uses multistream at various places:
- a
- b
- c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should still go after Multistream is introduced.
as necessary. The [protocol negotiation](../core-abstractions/connections#protocol-negotiation) | ||
and [upgrade process](../core-abstractions/connections#upgrading-connections) are explained | ||
further in the [connections document](../core-abstractions/connections.md). | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should add a sentence saying that it's also used to select application protocols spoken on streams.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 done with the last 3 commits.
Co-authored-by: Marten Seemann <[email protected]>
@p-shahi good to merge from my side. |
Context
Latest preview
Not against master (setting this up).