Hi, On Fri, Nov 10, 2017 at 05:39:46PM +0100, François Kooman wrote: > Parsing CSV can be cumbersome in depending software, so instead > offer JSON as well using "status 4". > > The "status 4" command uses the same keys/values as "status 2" > and "status 3", just formatted as JSON.
So... we had a nice and long discussion about this last year, which I
think can be wrapped like this
- JSON is nice because good parser support exist on the receiving end
today
- human readability is a plus for manually verifying output
- if we do JSON, we should do it for management *and* status file
- most voices argued for "do not require an external library"
(for *creation*). Not sure if we managed to convince David in
the end, though :-)
... but then it just died off, and the patch is sitting in patchwork
(where I moved it to "changes requested" just now).
Is there interest in moving forward, or shall we just let it go?
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany g...@greenie.muc.de
signature.asc
Description: PGP signature
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
