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

Use multiaddrs instead of UNIX socket paths for daemon sockets #5

Closed

Tracked by

vasco-santos opened this issue Feb 19, 2019 · 1 comment

Closed

Tracked by

Use multiaddrs instead of UNIX socket paths for daemon sockets #5

vasco-santos opened this issue Feb 19, 2019 · 1 comment

Member

vasco-santos commented Feb 19, 2019

The current implementation of js-libp2p-daemon expects unix socket paths, while go-libp2p-daemon has evolved to use multiaddrs for these paths.

In this context, js-libp2p-daemon-client, should be able to deal with multiaddrs. This feature also allows using TCP sockets on windows.

Reference:

The text was updated successfully, but these errors were encountered:

vasco-santos mentioned this issue

Enable windows job on travis libp2p/interop#5

Closed

3 tasks

Member Author

vasco-santos commented Mar 26, 2019

Implemented on #6

vasco-santos closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment