[Interop-dev] NetJSON Graph/Routes and weight data

[Nemesis]

I'm not really sure of either.

I opened a new issue in which I added a third option:
https://github.com/interop-dev/netjson/issues/18

Federico


On 07/03/2015 07:04 PM, Henning Rogge wrote:
> Do you really want to add some kind of mapping table for each possible
> routing metric value?
>
> Henning
>
> On Fri, Jul 3, 2015 at 7:03 PM, Nemesis <(spam-protected)> wrote:
>> On 07/03/2015 06:51 PM, Henning Rogge wrote:
>>
>> On Fri, Jul 3, 2015 at 6:45 PM, Nemesis <(spam-protected)> wrote:
>>
>>> Wouldn't it be possible for the implementing app to interpret the number
>>> and
>>> convert it to a meaningful human readable text representation?
>> No, because it depends on the routing metric.
>>
>>> Could you cite a complete example?
>> olsrd2 might give you a link cost of 2048... which represents "1 MBit/s".
>>
>> olsrd1 might give you 350... which represents "ETX 3.5".
>>
>>
>> So, if I'm not wrong, the way to interpret the number doesn't have to be
>> repeated for each link, it would probably be enough to have one attribute
>> for the entire NetworkGraph object. What do you think?
>>
>> Federico