[Interop-dev] [BMXd] make metric a optional property of NetworkRoutes, NetworkGraph, and each Route object

[Mitar]

Hi!

>> one of the reason why I prefer the "multiple NetworkGraph/-Route"
>> objects is that there is no guarantee that every topology has the same
>> links or even nodes.
> 
> Mm.. I did not know this. I can imagine this being common for different
> graphs representing ipv4 and ipv6, but even for different metrics?

Is it definitely true in wlan slovenija network as we are migrating from
OLSR to Babel. So some nodes have only OLSR daemon, some both, some just
Babel.

>> Some of them might only participate in one topology, there doesn't
>> even need to be a "full" topology.
> 
> Surely in this type of case wrapping the items in a collection object is
> the best approach.

I think this is a question of should the producer of JSON be smart and
do something more complicated, or should the consumer be smart. I think
in this case producer should not be smart and make it so that it is
simple to generate the file. We can always provide libraries to parse
JSON files in some easier way, if it there are common tasks for
consumers to do (like showing all links from a node no matter the
routing protocol).


Mitar

-- 
http://mitar.tnode.com/
https://twitter.com/mitar_m