You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After asking about tagging peers on twitter, I was redirected to 2 issues related to the connection manager functionality in go-libp2p (1 and 2). These issues brought to my attention the js equivalent of the go connection manager, js-libp2p-connection-manager. This module manages connections to peers. However, it is lacking some of the functionality that the Go connection manager has.
Currently, I have copied over the peer class from the js-libp2p-floodsub as a temporary measure. However, I would have to manually add a lot of the functionality and I don't think it is worth the extra effort. My current thoughts are either to use js-libp2p-connection-manager as a super class and add the needed functionality (tagging,etc) and later on make a PR to the js-libp2p-connection-manager. Or make a PR to the js-libp2p-connection-manager to include some of this functionality before using it in our codebase.
The text was updated successfully, but these errors were encountered:
After asking about tagging peers on twitter, I was redirected to 2 issues related to the connection manager functionality in go-libp2p (1 and 2). These issues brought to my attention the js equivalent of the go connection manager, js-libp2p-connection-manager. This module manages connections to peers. However, it is lacking some of the functionality that the Go connection manager has.
Currently, I have copied over the peer class from the js-libp2p-floodsub as a temporary measure. However, I would have to manually add a lot of the functionality and I don't think it is worth the extra effort. My current thoughts are either to use js-libp2p-connection-manager as a super class and add the needed functionality (tagging,etc) and later on make a PR to the js-libp2p-connection-manager. Or make a PR to the js-libp2p-connection-manager to include some of this functionality before using it in our codebase.
The text was updated successfully, but these errors were encountered: