Skip to content
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.

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

Replace network communication layer from nng (nanomsg) to libp2p #234

Open
satindergrewal opened this issue Jun 23, 2021 · 1 comment
Open
Assignees
Labels
enhancement New feature or request

Comments

@satindergrewal
Copy link
Collaborator

We should consider utilising libp2p in bet as per my understanding it will make p2p connections over different networks bit easier.

libp2p has many different modules to cover different scenarios, one of which peer-id based connections/communication seemed interesting to me:

Here's the link to C++ implimentation of libp2p: cpp-libp2p

@satindergrewal satindergrewal added the enhancement New feature or request label Jun 23, 2021
@satindergrewal satindergrewal self-assigned this Jun 23, 2021
@sg777
Copy link
Collaborator

sg777 commented Oct 3, 2021

To add to this, atm we are the backend nodes are communicating using pub-sub, push-pull sockets.

  1. In pub-sub communication dealer node is acting as publisher and all other nodes in the system are acting as subscribers.
  2. In push-pull communication, all nodes push the info to the dealer.

This front end version of this issue is here chips-blockchain/pangea-poker#495.

So basically the expectation is to have a system which doesn't need any static IP's in order to play the game. To start with we can create a POC where we can connect to backend from GUI using REST API's without websockets and then in the backend we use DHT for the communications.

Any ideas on this are most welcome, please feel free to ask for any clarity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants