[Olsr-dev] JSON info dump complete

[Teco Boot]

Op 15 mei 2012, om 18:25 heeft Henning Rogge het volgende geschreven:

> On Fri, May 11, 2012 at 3:59 PM, Hans-Christoph Steiner
> <(spam-protected)> wrote:
>> The central goal of the jsoninfo is to deliver the data in a parsable format that is good for programs to read.  It is the up to the program that is using the data to represent the data to the user.  If people want olsrd-generated human-readable data, they can already use httpinfo and txtinfo.
>> 
>> The data should be represented consistently with each unique data point only represented once.  Having multiple representations of the same data point just adds confusion for the person trying to figure out what's what.
>> 
>> Also towards the aim of consistency, I have standardized all time data points to be in milliseconds.  If there are other common data types, they should also use the same units.  Can anyone point out other such data types?  Are various "cost" data points in the same unit?  Are they directly comparible? If so, they could all just be called "cost", and then the rest of the info would be conveyed on context within a "routes" array entry, "links" array entry, etc.
> 
> The raw (integer) cost is always a value between 0 and 2^24-1
I say between 1 and 2^24-1
> 
> for a
> link and a value between 0 and 2^32-1
I say between 1 and 2^32-255

I say max_value is for useless links / routes. 2^32-1 could be used for useless route.

Teco

> for a route. Each plugin
> provides its own human readable representation for it (which would be
> useful if we use this json to generate a webpage).
> 
> Henning Rogge
> 
> -- 
> Steven Hawkings about cosmic inflation: "An increase of billions of
> billions of percent in a tiny fraction of a second. Of course, that
> was before the present government."
> 
> -- 
> Olsr-dev mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-dev