From owner-freebsd-arch@FreeBSD.ORG Wed Jul 30 01:51:55 2014 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4CD23727 for ; Wed, 30 Jul 2014 01:51:55 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 34FEA2439 for ; Wed, 30 Jul 2014 01:51:54 +0000 (UTC) Received: from u10-2-16-021.office.norse-data.com (unknown [50.204.88.51]) by elvis.mu.org (Postfix) with ESMTPSA id 368DB346DE1C for ; Tue, 29 Jul 2014 18:51:54 -0700 (PDT) Message-ID: <53D85001.4030707@mu.org> Date: Tue, 29 Jul 2014 18:53:05 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: freebsd-arch@freebsd.org Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML References: <20140725044921.9F0D3580A2@chaos.jnpr.net> <20140728054217.AC1A0580A2@chaos.jnpr.net> <20140728055336.GJ50802@ivaldir.etoilebsd.net> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jul 2014 01:51:55 -0000 On 7/28/14 11:29 PM, Adrian Chadd wrote: > On 28 July 2014 23:03, Jos Backus wrote: >> On Jul 28, 2014 10:57 PM, "Adrian Chadd" wrote: >>> Holy ... ! >>> >>> What really matter is whether the library API that you're going to >>> shoehorn into plenty of utilities is expressive enough to express a >>> whole bunch of different output types. >>> >>> So it doesn't matter if you want JSON, or YAML, or XML, or the native >>> tool output. The trick is whether the library API is good enough. >>> >>> So if you want to win people over, just make sure it gets adopted >>> throughout other tools. :) >> Wouldn't the API be a way to build up an in-memory combination of lists and >> maps in most cases, which then gets serialized out at emission time? Kind of >> like calling object.to_yaml, where object is a Hash, but in C? >> > Not everything can be buffered like that over time. Time series data > may have stuff buffered up during an output / sample period (eg the > one a second output from vmstat 1) Yup, exactly! This is very much needed and will be part of the gsoc project being worked on. -Alfred > > -a > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" >