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

Indirect routing #297

Open
elgohr opened this issue Feb 18, 2021 · 0 comments
Open

Indirect routing #297

elgohr opened this issue Feb 18, 2021 · 0 comments

Comments

@elgohr
Copy link

elgohr commented Feb 18, 2021

test

The example above describes a scenario with 3 peers. One acts as a provider and two clients would like to get information from that provider. Due to network restrictions only one of the two clients is able to communicate with the provider, but both clients are able to connect to each other.

After estabilishing the network, kademlia.New().Discover() shows the correct routes.

Provider knows Allowed_Client
Allowed_Client knows Provider and Blocked_Client
Blocked_Client knows Allowed_Client

In this scenario it would be great to have a way that SendMessage would use id node.ID instead of addr string.
E.g.: SendMessage(ctx context.Context, id ID, msg Serializable) error
In this way Blocked_Client could send a message to Provider without knowing that it has to pass Allowed_Client.

At the moment this has to be done somehow manually. To me this is somehow strange, as the routing is already implemented and correct.

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

No branches or pull requests

1 participant