libp2p / libp2p/js-libp2p-daemon
Support websockets for control
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 17
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
A copy of https://github.com/libp2p/go-libp2p-daemon/issues/60
If we change the socket path to be a multiaddr and then create unix socket listening as just another libp2p transport, we could determine our appropriate control transport based on the multiaddr, similar to how libp2p already operates.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the referenced go-libp2p-daemon issue and the js-libp2p-daemon control transport implementation. Determine how the socket path can become a multiaddr and how Unix sockets are represented as a libp2p transport. Done means control transport selection follows the multiaddr and WebSocket support works alongside Unix sockets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100