-
Notifications
You must be signed in to change notification settings - Fork 47
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
rfc: Merged path #73
Comments
@TobleMiner I'd like to implement this. |
or at all? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unlike routers, supernodes support being part of multiple domains at once.
There is information that does and other that does not change per domain.
I'd like to propose something like a merged path, one may request to get all information properly squashed into one struct.
Things that are the same across all interfaces like
firmware
orbatman-adv
would stay a simple field,while others that differ, would become a sorted concatenation of entries.
Two domains having
mesh
withbatN
andbatM
respectively would become batN, batM.This is easy enough, where the provide info are either the same across different interfaces, or contain different keys.
The difficulty arises on a path like
system.domain_code
which does contain different values but the same key across interfaces.One possible solution would be to provide
system.domain_codes
instead, which would contain a list of strings instead of one.The same goes for
node_id
.I'd be happy to see some feedback on this; especially, whether this is beyond scope of mesh-announce @TobleMiner .
The text was updated successfully, but these errors were encountered: