Skip to content
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

MultiAddr problem #166

Closed
driftluo opened this issue Jun 7, 2019 · 0 comments
Closed

MultiAddr problem #166

driftluo opened this issue Jun 7, 2019 · 0 comments
Labels
t:question Type: Request answer or open discussion.

Comments

@driftluo
Copy link
Collaborator

driftluo commented Jun 7, 2019

With the use of Multiaddr, the official itself has also found some problems, and there are problems with their own descriptions that are missing and inaccurate, and there are proposals to solve them by some means.

Parity In the case that the proposal has not yet passed, a non-standard protocol such as x-parity-ws has been added for practical needs.

Now, we have to rethink, what are our real needs for this increasingly complex specification, and whether we need to really go further and further with non-standard or complex standards.

ref: multiformats/multiaddr#87
ref: libp2p/rust-libp2p#1093

@driftluo driftluo added the t:question Type: Request answer or open discussion. label Jun 7, 2019
@doitian doitian closed this as completed Jul 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t:question Type: Request answer or open discussion.
Projects
None yet
Development

No branches or pull requests

2 participants