[B.A.T.M.A.N.] [PATCH] Add switch for vis daemon to serve mesh topology in JSON format - TAKE 2

[Antoine van Gelder]

Apologies, I'm not sure why that got mangled, let's try that again.

 - antoine

--

Patch attached for review.

NOTES



* Data is served in the format



 e.g.

   HTTP/1.0 200 OK
   Content-type: application/json

   [
       { router : "10.0.0.5", neighbour : "10.0.0.3", label : 1.01 },
       { router : "10.0.0.5", neighbour : "10.0.0.6", label : 1.00 },
       { router : "10.0.0.5", neighbour : "10.0.0.1", label : 1.00 },
       { router : "10.0.0.3", neighbour : "10.0.0.5", label : 1.00 },
       { router : "10.0.0.3", neighbour : "10.0.0.1", label : 1.00 },
       { router : "10.0.0.3", neighbour : "10.0.0.6", label : 1.00 },
       { router : "10.0.0.6", neighbour : "10.0.0.5", label : 1.00 },
       { router : "10.0.0.6", neighbour : "10.0.0.3", label : 1.00 },
       { router : "10.0.0.6", neighbour : "10.0.0.1", label : 1.00 },
       { router : "10.0.0.1", neighbour : "10.0.0.3", label : 1.00 },
       { router : "10.0.0.1", neighbour : "10.0.0.5", label : 1.00 },
       { router : "10.0.0.1", neighbour : "10.0.0.6", label : 1.03 },

   ]


Thank you Marek!

- antoine

* -j turns on JSON mode and closes the socket after serving the browser request. [ { router : "d.d.d.d", neighbour|gateway : "d.d.d.d", label : d.dd|"HNA" }, ... ] { router : "10.0.0.1", gateway : "0.0.0.0/0.0.0.0", label : "HNA" }

vis.diff
Description: Binary data