From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Sun, 08 Sep 2013 10:47:00 +0200 Message-ID: <87ppsj66pn.wl%nils@nilsschneider.net> From: Nils Schneider In-Reply-To: <201309081039.23458.lindner_marek@yahoo.de> References: <1378585186-7970-1-git-send-email-nils@nilsschneider.net> <20130907203207.GN1570@ritirata.org> <87hadw1hbs.wl%nils@nilsschneider.net> <201309081039.23458.lindner_marek@yahoo.de> MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Subject: Re: [B.A.T.M.A.N.] [PATCH] alfred: output valid JSON Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking 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