Skip to content

Conversation

@vasco-santos
Copy link
Member

@vasco-santos vasco-santos commented Oct 5, 2020

In the context of Improving libp2p discoverability and connectivity (#703), this PR integrates the new rendezvous implementations. This is the initial step for the discovery API, which is described in #768 and will have follow up PRs.

This PR integrates rendezvous as described in https://github.com/libp2p/js-libp2p-rendezvous/blob/feat/rendezvous-protocol-full-implementation/LIBP2P.md. The rendezvous module is provided in the libp2p config, and properly started and stopped with the node. Moreover, docs on how to configure a libp2p node acting as a rendezvous server, as well as a rendezvous client were added.

Needs:

Follow up work:

In the context of #768 , libp2p will provide a service discovery API, which will leverage the rendezvous if provided, content routing, and possibly other modules in the future. Once we have the discovery work done, it will be important to create a new example with the discovery API and rendezvous. Moreover, production guides for the server should be created

// Create rendezvous if provided
if (this._modules.rendezvous) {
const Rendezvous = this._modules.rendezvous
this.rendezvous = new Rendezvous({
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Considering that we will provide the libp2p.discovery API, I am thinking wether we should provide libp2p.rendezvous, or just leave it as libp2p._rendezvous. Thoughts?
If we keep this as it is, this PR should include API docs for rendezvous

@vasco-santos vasco-santos force-pushed the feat/rendezvous-integration branch from 699b4e5 to f5b6ebe Compare November 9, 2020 14:13
Base automatically changed from 0.30.x to master December 16, 2020 12:56
@vasco-santos
Copy link
Member Author

Replaced by #856

@vasco-santos vasco-santos deleted the feat/rendezvous-integration branch January 5, 2021 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants