ipfs/kubo

Configurable multiplexers

Open

#4893 opened on Mar 29, 2018

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
help wantedkind/enhancement

Description

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).

Contributor guide

Tech stack
go
Domain
backendinfrastructure
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programming knowledgeUnderstanding of IPFS multiplexers (mplex/yamux)Familiarity with go ipfs config structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
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.