From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Text-based IPC for Userspace Implementations
Date: Wed, 17 May 2017 20:07:41 +0200 [thread overview]
Message-ID: <87wp9fuzki.fsf@alrua-karlstad> (raw)
In-Reply-To: <CAHmME9o-PM0ma0E5tF868fBCmOfoSdJ8BYA+_Enbbq89t900+w@mail.gmail.com> (Jason A. Donenfeld's message of "Wed, 17 May 2017 16:00:17 +0200")
"Jason A. Donenfeld" <Jason@zx2c4.com> writes:
> Hello list,
>
> Re:JSON --
>
> JSON is difficult to parse and requires large libraries, especially
> for something like JSON-RPC. I'd rather not have these dependencies or
> complications.
>
> On the contrary, a simple key=value newline scheme can be parsed
> trivially by anyone in a safe way, and allows for very quick in basic
> implementations in nearly all environments, even bash. Even given a
> JSON library, a stream of key=value is considerably easier and more
> flexible in the parsing stage.
My point was not so much "just use JSON". My point was "you are
disguising something that requires stateful parsing as a simple
key/value scheme, which is bound to lead to bugs eventually". I.e. if
someone were to write a parser that would (e.g.) just grep for a public
key, they'd end up with ambiguous results at best.
-Toke
next prev parent reply other threads:[~2017-05-17 17:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 12:36 Text-based IPC for Userspace Implementations Jason A. Donenfeld
2017-05-16 13:12 ` Toke Høiland-Jørgensen
2017-05-16 16:01 ` Jonathan Rudenberg
2017-05-16 16:09 ` Toke Høiland-Jørgensen
2017-05-16 19:26 ` Jörg Thalheim
2017-05-17 14:01 ` Jason A. Donenfeld
2017-05-17 14:04 ` Manuel Schölling
2017-05-17 14:08 ` Jason A. Donenfeld
2017-05-18 16:46 ` Manuel Schölling
2017-05-18 18:04 ` Daniel Kahn Gillmor
2017-05-17 14:14 ` Bzzzz
2017-05-17 14:17 ` Jason A. Donenfeld
2017-05-16 16:33 ` Guanhao Yin
2017-05-17 13:53 ` Jason A. Donenfeld
2017-05-16 15:43 ` Ivan Labáth
2017-05-17 14:00 ` Jason A. Donenfeld
2017-05-17 18:07 ` Toke Høiland-Jørgensen [this message]
2017-05-17 18:10 ` Jason A. Donenfeld
2017-05-17 17:04 ` Jason A. Donenfeld
[not found] ` <20170516154204.GB9458@matrix-dream.net>
[not found] ` <CAHmME9roTAqMYB0qB7JG3rkKfGw1nfzTz0AD-frcGyyweCTcJQ@mail.gmail.com>
2017-05-18 8:02 ` allowed_ips move semantics? Ivan Labáth
2017-05-18 10:08 ` Jason A. Donenfeld
2017-05-18 12:00 ` Ivan Labáth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wp9fuzki.fsf@alrua-karlstad \
--to=toke@toke.dk \
--cc=Jason@zx2c4.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.