From: "Jörg Thalheim" <joerg@higgsboson.tk>
To: wireguard@lists.zx2c4.com
Subject: Re: Text-based IPC for Userspace Implementations
Date: Tue, 16 May 2017 20:26:53 +0100 [thread overview]
Message-ID: <1500fe21-c423-b34d-adf5-463b5d483cbf@higgsboson.tk> (raw)
In-Reply-To: <358B5193-8D9F-472F-8202-B81BAA022FDD@titanous.com>
On 2017-05-16 17:01, Jonathan Rudenberg wrote:
>> On May 16, 2017, at 09:12, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>>
>> 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/3401e8d1e1300742ed41910b9338b9da52689a16/tools/perf/pmu-events
>
> Jonathan
For the kernel, netlink will be used, which is already does its own serialization format. The use of JSON here, would not make sense here.
next prev parent reply other threads:[~2017-05-16 19:15 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
2017-05-16 16:09 ` Toke Høiland-Jørgensen
2017-05-16 19:26 ` Jörg Thalheim [this message]
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=1500fe21-c423-b34d-adf5-463b5d483cbf@higgsboson.tk \
--to=joerg@higgsboson.tk \
--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).