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
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 or batman-adv would stay a simple field,
while others that differ, would become a sorted concatenation of entries.
Two domains having mesh with batN and batM 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:
@TobleMiner I'd like to implement this.
The remaining question is where.
Either I do it in my related rust project, or, If you think this is in-scope of mesh-announce, I'll do it here in python.
Please decide soon.
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: