search

libp2p / js-libp2p-webtransport

WebTranport module that libp2p uses and that implements the interface-transport spec
Other
15 stars 5 forks source link

Use go-libp2p-daemon instead of building webtransport server #75

Open p-shahi opened 1 year ago

p-shahi commented 1 year ago

Update go-libp2p-daemon to the latest libp2p which will give it webtransport support, then we can use a precompiled binary and not have to build the webtransport server in this repo from source - https://github.com/libp2p/go-libp2p-daemon/pull/281

Originally posted by @achingbrain in https://github.com/libp2p/js-libp2p-webtransport/issues/67#issuecomment-1527583233

p-shahi commented 1 year ago

Needs: https://github.com/libp2p/go-libp2p-daemon/pull/281

MarcoPolo commented 1 year ago

I think keeping the webtransport server here is preferable to using the go-libp2p-daemon. The problem linked in the comment would not have been solved by using go-libp2p-daemon.

The problem linked would have been solved simply by pinning the Go toolchain used in CI.

MarcoPolo commented 1 year ago

I'd argue in favor of #67 (but calling it pinning to Go toolchain) rather than this. I don't want to invest more into go-libp2p-daemon for this use case.