rfc: dynamic affinity routing - #15
Open
alanshaw wants to merge 1 commit into
Open
Conversation
Copilot AI
added a commit
to fil-forge/libforge
that referenced
this pull request
Aug 1, 2026
Per RFC fil-one/RFC#15 (dynamic affinity routing), adds an optional `affinity` field to `AddArguments` that accepts a list of storage-node DIDs. When present, it constrains routing to the specified nodes. Regenerates cbor_gen.go and json_gen.go accordingly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📖 Preview
Summary
Proposal for an alternative to the presupposed "static" affinity routing where ALL writes to a given space are routed to a specific storage node.