[Interop-dev] Network Topology JSON [was: OLSRd2 JSON APIs]

[Henning Rogge]

On Sun, Nov 23, 2014 at 4:26 PM, Mitar <(spam-protected)> wrote:
> Hi!
>
>>> Should it be string, int, or float?
>>
>> Cost should be "int" in my opinion, makes post-processing easier.
>
> I think it is easier to cast to int on the consumer side where you can
> decide in various ways what you want to do with the value. I think this
> is just a transport format.
>
> How you map ETX to int?

Multiplying it by a factor of X... for example multiplying by 1000.

OLSR (both v1 and v2) doesn't use floating point numbers internally anyways.

Henning