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

Client Routing Table #46

Open
Tracked by #54
iand opened this issue Jun 30, 2023 · 1 comment
Open
Tracked by #54

Client Routing Table #46

iand opened this issue Jun 30, 2023 · 1 comment
Labels
kind/enhancement New feature or request scope/nicetohave Nice to have feature going beyond go-libp2p-kad-dht

Comments

@iand
Copy link
Contributor

iand commented Jun 30, 2023

ETA: 2023-09-01

Implement an optimized routing table for DHT clients

@iand iand added kind/enhancement New feature or request scope/required Feature required to match go-libp2p-kad-dht labels Jun 30, 2023
@iand iand mentioned this issue Jun 30, 2023
3 tasks
@guillaumemichel
Copy link
Contributor

Changing the scope to nicetohave.

The DHT clients can use the server (default) routing table, it is the case in go-libp2p-kad-dht. Having a client routing table is a client optimization.

@guillaumemichel guillaumemichel added scope/nicetohave Nice to have feature going beyond go-libp2p-kad-dht and removed scope/required Feature required to match go-libp2p-kad-dht labels Jun 30, 2023
@iand iand moved this to Unplanned in DHT Optimization Jul 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request scope/nicetohave Nice to have feature going beyond go-libp2p-kad-dht
Projects
Status: Unplanned
Development

No branches or pull requests

2 participants