All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nicolás Echániz" <nicoechaniz@altermundi.net>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Alfred batadv-vis json conformance
Date: Sun, 06 Oct 2013 10:35:36 +0200	[thread overview]
Message-ID: <525120D8.10508@altermundi.net> (raw)
In-Reply-To: <20131002133600.GD16339@lunn.ch>

El 02/10/13 15:36, Andrew Lunn escribió:
> 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 format
>> 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.
> 
> 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



  reply	other threads:[~2013-10-06  8:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-01 20:26 [B.A.T.M.A.N.] Alfred batadv-vis json conformance Andrew Lunn
2013-10-02 13:05 ` Simon Wunderlich
2013-10-02 13:36   ` Andrew Lunn
2013-10-06  8:35     ` Nicolás Echániz [this message]
2013-10-07  9:00       ` Andrew Lunn
2013-10-02 16:01   ` Antonio Quartulli
2013-10-03  6:09     ` Martin Hundebøll
2013-10-03  8:11       ` Andrew Lunn
2013-10-03  8:22         ` Antonio Quartulli
2013-10-03  8:53           ` Andrew Lunn
2013-10-03  9:00             ` Antonio Quartulli
2013-10-03  9:05               ` Andrew Lunn

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=525120D8.10508@altermundi.net \
    --to=nicoechaniz@altermundi.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.