Document "Smart Dialing"
@p-shahi 已经在做这个了。
开始于 2023年8月17日。
评估
这个 Issue 还没有评估数据。
描述
libp2p implementations support a wide range of transport protocols (TPC, QUIC, WebSockets, WebTransport, WebRTC (upcoming.)) A libp2p node will have a multiaddr for each transport protocol it supports.
When a libp2p node tries to connect to a peer, it receives the peer's multiaddr list, and selects a multiaddr to dial/connect with.
Currently, this selection is not optimized.
As libp2p implementations support more transports (and as more metadata gets stuffed into multiaddrs), a node's multiaddr list will grow much larger.
Therefore, the go-libp2p implementation is planning to introduce improvements to dialing beginning end of Q4 2022.
Done Criteria
- Documentation describing these optimizations exist (to be decided: as its own doc under a new "Advanced Concepts" section, other existing relevant docs link to it)
- https://github.com/libp2p/docs/issues/216
- Document QUIC Blackhole detector (issue to be created)
- Document RTT estimation (issue to be created)
Why Important
Users should know and understand how libp2p decides to select which peer multiaddr to dial, how it picks which addr will result in the most performant & successful connection, and why this matters (conservative optimizations are used to reduce a burden on resources.)
- 主要语言
- HTML
- 星标
- 72
- 派生
- 96
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
libp2p/docs 的其他 Issue
-
Broken Link未关闭
难度 1/5 1 小时以内 新手友好度 68/100
-
难度 1/5 1 小时以内 新手友好度 65/100
-
难度 2/5 1-3 小时 新手友好度 55/100
-
难度 5/5 一周以上 新手友好度 25/100
-
难度 3/5 1-2 天 新手友好度 45/100