From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <525120D8.10508@altermundi.net> Date: Sun, 06 Oct 2013 10:35:36 +0200 From: =?ISO-8859-1?Q?Nicol=E1s_Ech=E1niz?= MIME-Version: 1.0 References: <20131001202648.GT11097@lunn.ch> <20131002130548.GA24077@pandem0nium> <20131002133600.GD16339@lunn.ch> In-Reply-To: <20131002133600.GD16339@lunn.ch> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Re: [B.A.T.M.A.N.] Alfred batadv-vis json conformance 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: b.a.t.m.a.n@lists.open-mesh.org El 02/10/13 15:36, Andrew Lunn escribi=F3: > On Wed, Oct 02, 2013 at 03:05:48PM +0200, Simon Wunderlich wrote: >> Hey Andrew, >> >> On Tue, Oct 01, 2013 at 10:26:48PM +0200, Andrew Lunn wrote: >> Yes, it is only JSON line-wise, but not the whole output. This output fo= rmat >> however is the same as we have/had in the batctl JSON output which comes >> from the kernel (I think that was your contribution in the first place?). >> >> Therefore I'd like to leave this old format as it is to allow communities >> to seamlessly switch from batctl json vis to alfred-vis. >=20 > That is what i was expecting. So when i did the first implementation > this morning, i added a new format, cjson, for conforming json. Not > the best of names, but i could not think of anything better. maybe jsondoc would be more explicit, as it differentiates the output from the current json(lines) format. cheers, Nico