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

[Mitar]

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?


Mitar

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