From: Nils Schneider <nils@nilsschneider.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH] alfred: output valid JSON
Date: Sun, 08 Sep 2013 10:47:00 +0200 [thread overview]
Message-ID: <87ppsj66pn.wl%nils@nilsschneider.net> (raw)
In-Reply-To: <201309081039.23458.lindner_marek@yahoo.de>
The current output format of alfred -r looks like this:
{ "fe:f1:00:00:01:01", "OpenWRT-node-1\x0a" },
{ "fe:f1:00:00:02:01", "OpenWRT-node-2\x0a" },
{ "fe:f1:00:00:03:01", "OpenWRT-node-3\x0a" },
It's not clear how one should parse this as there is no documentation
except the source code.
With my patch, it'll look like this:
{
"fe:f1:00:00:01:01": "OpenWRT-node-1\u000a",
"fe:f1:00:00:02:01": "OpenWRT-node-2\u000a",
"fe:f1:00:00:03:01": "OpenWRT-node-3\u000a"
}
This is JSOΝ which is well documented and thus can be parsed
easily. It's a dictionary with the node's ID as the key and the data
as value.
At Sun, 8 Sep 2013 10:39:23 +0800,
Marek Lindner wrote:
>=20
> On Sunday, September 08, 2013 04:56:39 Nils Schneider wrote:
> > The current output format isn't really broken, just tricky to parse.
> > I decided to make it valid JSOΝ as it was already pretty close. This
> > allows parsing with virtually any programming language.
>=20
> Please be more specific about what was broken and how your fix addresses =
the=20
> problem. An example would be nice too.
>=20
> Cheers,
> Marek
next prev parent reply other threads:[~2013-09-08 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 20:19 [B.A.T.M.A.N.] [PATCH] alfred: output valid JSON Nils Schneider
2013-09-07 20:32 ` Antonio Quartulli
2013-09-07 20:56 ` Nils Schneider
2013-09-08 2:39 ` Marek Lindner
2013-09-08 8:47 ` Nils Schneider [this message]
2013-09-08 21:53 ` Simon Wunderlich
2013-09-08 23:40 ` Gui Iribarren
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=87ppsj66pn.wl%nils@nilsschneider.net \
--to=nils@nilsschneider.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/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.