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

#0037 Disjoint Sections #2

Open
david-maidsafe opened this issue Sep 3, 2018 · 0 comments
Open

#0037 Disjoint Sections #2

david-maidsafe opened this issue Sep 3, 2018 · 0 comments
Labels
RFC RFC Issue - used for tracking through process on Project board

Comments

@david-maidsafe
Copy link
Owner

Disjoint Sections

Introduce the notion of a "section" of the network, in addition to the existing notion of a group, and the corresponding routing table logic, such that the network's sections are disjoint and form a partition of the set of nodes. Each node will thus be a member of exactly one section. The section size, however, will not be fixed, as opposed to the group size.
Groups will continue to be usable, though, and might remain the appropriate notion for safe_vault's tasks.
(This RFC was originally called "Disjoint Groups", but it turns out to be useful to keep both the old and the new kind of "group" functionality in the code for different purposes. The new concept is therefore called a "section", and the GROUP_SIZE closest nodes to a given address continue to be called the "close group" of that address.)

📘 https://github.com/david-maidsafe/rfcs/blob/master/text/0037-disjoint-groups/0037-disjoint-groups.md

@david-maidsafe david-maidsafe added the RFC RFC Issue - used for tracking through process on Project board label Sep 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RFC RFC Issue - used for tracking through process on Project board
Projects
None yet
Development

No branches or pull requests

1 participant