Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support websockets for control #3

Open
jacobheun opened this issue Jan 30, 2019 · 0 comments
Open

Support websockets for control #3

jacobheun opened this issue Jan 30, 2019 · 0 comments
Labels
exp/expert Having worked on the specific codebase is important kind/enhancement A net-new feature or improvement to an existing feature P3 Low: Not priority right now

Comments

@jacobheun
Copy link
Contributor

A copy of libp2p/go-libp2p-daemon#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.
@jacobheun jacobheun added kind/enhancement A net-new feature or improvement to an existing feature exp/expert Having worked on the specific codebase is important P3 Low: Not priority right now labels Jan 30, 2019
@jacobheun jacobheun mentioned this issue Jan 30, 2019
Closed
@saul-jb saul-jb mentioned this issue Sep 10, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
exp/expert Having worked on the specific codebase is important kind/enhancement A net-new feature or improvement to an existing feature P3 Low: Not priority right now
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jacobheun