Implement needed functionality in JS libp2p libraries about js-libp2p-gossipsub HOT 7 CLOSED

libp2p/js-libp2p-pubsub got its inital release and there is a PR for integrating it wth floodsub implementation libp2p/js-libp2p-floodsub#69.

We now can iterate on js-libp2p-pubsub implementation, according to other needs of gossipsub, as well as to improve documentation and add an example, as gossipsub is being implemented.

Important note: we will have to migrate both codebases (floodsub and pubsub) to use async iterators, instead of callbacks, and by then level up our documentation. When I get to the async iterators, I will have to prioritize the DHT, but in the second step I will go with the pubsub modules. Anyway, I would recommend that you guys start with async iterators if you are confortable, otherwise you will need to refactor this implementation afterward.

from js-libp2p-gossipsub.

@vasco-santos beautiful! Thanks for getting on this so quickly 💪

from js-libp2p-gossipsub.

After the call with the libp2p team, they will be extracting the base protocol from js-libp2p-floodsub so that it can be used to build other protocols on top of the base protocol.

They are also in the process of writing interoperability tests for libp2p modelled on the ipfs interoperability tests. In the meantime, we can use the js-libp2p-daemon and go-libp2p-daemon.

They are still working out the details of the connection manager. So, the work on that can be done later.

from js-libp2p-gossipsub.

CC @vasco-santos @jacobheun

from js-libp2p-gossipsub.

I will keep you posted regarding the base protocol and interop tests moves!

from js-libp2p-gossipsub.

Thank you very much @vasco-santos and @raulk. We will definitely be using async iterators moving forward and I will continue to give feedback to the js-libp2p-pubsub module.

from js-libp2p-gossipsub.

Done..

from js-libp2p-gossipsub.