> On Jul 21, 2017, at 1:10 PM, Leif Johansson <[email protected]> wrote: > > > We had a (less than spirited) discussion in Praha about the K/V vs JSON. > > The situation is that of the active participants that are also > implementors one (postfix - Victor) has said that he does not believe > that postfix will ship with a standard JSON-based implementation but > that this doesn't preclude third-party plugins. > > The other major implementor who is also an active participant (google) > has stated that they have a JSON implementation but that they are > also eager to close this issue. One more implementor (Chris) has stated > no preference but also said that his (native) JSON parser is somewhat > smaller than his K/V one. > > Based on this and falling back to the IETF WG process as chair I would > conclude that there isn't enough consensus to make a change and that > we are staying with JSON. > > I would prefer to have more opinions (implementors in particular) but > we are also going to get past this. In particular I would like to hear > from implementors who (like Victor) have a problem living with either > choice.
I don’t have an opinion on the two choices but in the past when I’ve needed to do JSON work in “C’, I’ve used this library which made it very painless. https://github.com/DaveGamble/cJSON <https://github.com/DaveGamble/cJSON> The license is very permissive (MIT) and the author even suggests just including two files cJSON.[ch] directly in your project if you wish. Tom
_______________________________________________ Uta mailing list [email protected] https://www.ietf.org/mailman/listinfo/uta
