ipfs/kubo

Configurable multiplexers

Open

#4,893 建立於 2018年3月29日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)Go (13,906 star) (2,725 fork)batch import
help wantedkind/enhancement

描述

It would be nice to be able to configure the supported multiplexers in the config. My thinking is to add a and a Multiplexers config option to the Swarm section. One tricky part is naming. For usability, a simple "mplex" or "yamux" would be nice however the full protocol name (with the version) may be a better option. Thoughts?

When we do this, I'd also like to get rid of the --enable-mplex-experiment flag as it's no longer an experiment (yeah, yeah, breaking changes... maybe keep it? Wait for https://github.com/ipfs/go-ipfs-cmds/issues/93?).

My eventual goal is to get rid of our "experimental" flags and move to config options. Ideally, the CLI should be stable (and minimal).

貢獻者指南

技術棧
go
領域
backendinfrastructure
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Go programming knowledgeUnderstanding of IPFS multiplexers (mplex/yamux)Familiarity with go ipfs config structure
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
Investigate the current config structure in go ipfs to determine where to add `Multiplexers` option. Review the linked discussion about naming conventions (e.g., simple 'mplex' vs full protocol name). Consider the breaking change of removing ` enable mplex experiment` flag and whether to keep it for compatibility. Examine issue #93 in go ipfs cmds for potential dependencies. Propose a config design that allows users to specify supported multiplexers and plan migration from the experimental flag.