Hi
> 3) I believe the output structure is not valid JSON with the "END"
> > string at the end.
>
> All (multiline) responses end with "END", so that's why I did that as
> well. Ideally I'd construct a JSON object that does not include newlines
> at all and just responds as:
>
> SUCCESS: { ... }
>
One of the niceties of JSON is its readability which is greatly reduced
if formatted without line breaks. Multi-line with the same
format used for management and console would be nice. Except the
former gets the extra footer line with "END".
Selva
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
