From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Todd Gill <tgill@redhat.com>, dm-devel@redhat.com
Subject: Re: [PATCH 0/1] add option to output JSON for multipathd command
Date: Wed, 4 May 2016 18:17:11 -0700 [thread overview]
Message-ID: <572A9F17.5080208@sandisk.com> (raw)
In-Reply-To: <1462393428-13929-1-git-send-email-tgill@redhat.com>
On 05/04/16 13:23, Todd Gill wrote:
> I had earlier sent an email to dm-devel proposing we add a feature
> in multipathd to output multipath map topology in JSON format. This
> patch contains to the code for that feature.
>
> Having an option for the CLI to output in JSON would allow higher
> level applications to more easily monitor/manage multipath.
>
> I thought it was best to take advantage of some of the existing
> snprintf_xxx functions rather than adding a library dependency
> to multipathd.
>
> Will add code for groups next if this is accepted.
XML is better standardized than JSON, so why to use JSON? An overview of
the advantages of XML is available on
http://www.yegor256.com/2015/11/16/json-vs-xml.html. A good overview of
JSON and also of some of its disadvantages is available on
https://en.wikipedia.org/wiki/JSON.
Sorry that I missed your previous e-mail about this topic.
Bart.
next prev parent reply other threads:[~2016-05-05 1:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 20:23 [PATCH 0/1] add option to output JSON for multipathd command Todd Gill
2016-05-04 20:23 ` [PATCH 1/1] add display of map information in JSON format Todd Gill
2016-05-05 13:16 ` Gris Ge
2016-05-04 23:22 ` [PATCH 0/1] add option to output JSON for multipathd command Alasdair G Kergon
2016-05-05 1:45 ` Todd Gill
2016-05-05 1:17 ` Bart Van Assche [this message]
2016-05-06 13:52 ` Todd Gill
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=572A9F17.5080208@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=dm-devel@redhat.com \
--cc=tgill@redhat.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 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.