On 05/04/2016 09:17 PM, Bart Van Assche wrote: > 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. > I was on the fence between XML and JSON. I think JSON is more simple. I'm not sure we'd need the features listed as advantages in the first link you sent. > Sorry that I missed your previous e-mail about this topic. > No problem. Thanks for the feedback. I'm interested in making the data easily available to higher level applications. So, any common/easily consumed data format would be fine. Todd -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
