From: Jonathan Rudenberg <jonathan@titanous.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: Re: Text-based IPC for Userspace Implementations
Date: Tue, 16 May 2017 12:01:17 -0400 [thread overview]
Message-ID: <358B5193-8D9F-472F-8202-B81BAA022FDD@titanous.com> (raw)
In-Reply-To: <87vap1gd2w.fsf@alrua-kau>
> On May 16, 2017, at 09:12, Toke H=C3=B8iland-J=C3=B8rgensen =
<toke@toke.dk> wrote:
>=20
> So why not avoid any possible confusion and just emit JSON? Or another
> well-established serialisation format where the nesting can be made
> explicit... :)
+1 to this, requiring implementors to also implement a custom =
serialization format will lead to avoidable bugs.
I took a quick look and there is a bit of precedent for the use of JSON =
in the kernel tree: =
https://github.com/torvalds/linux/tree/3401e8d1e1300742ed41910b9338b9da526=
89a16/tools/perf/pmu-events
Jonathan
next prev parent reply other threads:[~2017-05-16 15:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 12:36 Jason A. Donenfeld
2017-05-16 13:12 ` Toke Høiland-Jørgensen
2017-05-16 16:01 ` Jonathan Rudenberg [this message]
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
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=358B5193-8D9F-472F-8202-B81BAA022FDD@titanous.com \
--to=jonathan@titanous.com \
--cc=Jason@zx2c4.com \
--cc=toke@toke.dk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).