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

rfc: Merged path #73

Open
AiyionPrime opened this issue Mar 8, 2021 · 2 comments
Open

rfc: Merged path #73

AiyionPrime opened this issue Mar 8, 2021 · 2 comments

Comments

@AiyionPrime
Copy link
Contributor

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 .

@AiyionPrime
Copy link
Contributor Author

AiyionPrime commented Apr 2, 2021

@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.

@AiyionPrime
Copy link
Contributor Author

or at all?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant