You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Done criteria: It is possible to instantiate an IpfsDHT server that is able to return to users provider records from alternative sources than just the datastore Why important: This enables creating DHT server nodes with more sophisticated record management. In particular it will allow hydra nodes to store lots of addresses for peers without shoving them all into the libp2p host Notes:
This could be resolved by either adding more options to the ProviderManager or just having an interface for the provide manager that gets passed in as an option to the DHT. Note if taking the interface approach that we'll have to deprecate or remove
aschmahmann
changed the title
Add a "delegated content routing" aware ProvideManager
Extensible record storage/retrieval for the ProvideManager
Oct 14, 2021
aschmahmann
changed the title
Extensible record storage/retrieval for the ProvideManager
Extensible provider record storage/retrieval
Oct 14, 2021
Done criteria: It is possible to instantiate an IpfsDHT server that is able to return to users provider records from alternative sources than just the datastore
Why important: This enables creating DHT server nodes with more sophisticated record management. In particular it will allow hydra nodes to store lots of addresses for peers without shoving them all into the libp2p host
Notes:
go-libp2p-kad-dht/handlers.go
Line 325 in 5a8437e
go-libp2p-kad-dht/dht_options.go
Line 244 in 5a8437e
The text was updated successfully, but these errors were encountered: