ipfs/kubo

Configurable multiplexers

Open

#4,893 opened on Mar 29, 2018

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

Repository metrics

Stars
 (13,906 stars)
PR merge metrics
 (Avg merge 4d 2h) (28 merged PRs in 30d)

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

Research direction
Review the current multiplexer configuration and experiment flags in the Kubo config. Investigate how Swarm config options are structured, and propose a new Multiplexers field with user friendly names like "mplex" or "yamux". Consider the impact of removing the enable mplex experiment flag.
Tech stack
go
Domain
backend
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.
Clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30