Refactor predecessors and successors to hold RemoteNodeStates, not just NodeIDs #46
Labels
No labels
ActivityPub
advanced features
basic functionality
bug
DHT
evaluation
refactoring
security
test case
No milestone
No project
No assignees
1 participant
Notifications
Total time spent: 1 hour 50 minutes
Due date
schmittlauch
1 hour 50 minutes
No due date set.
Blocks
#44 periodic stabilise
schmittlauch/Hash2Pub
Reference: schmittlauch/Hash2Pub#46
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
At least immediate successors and predecessors need to be contacted directly. Relying on the cache to still hold the corresponding hostname and port is error-prone.
Also need to add an ordering.