From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Myqhz-0004op-Iv for qemu-devel@nongnu.org; Fri, 16 Oct 2009 13:35:19 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Myqhv-0004nU-4V for qemu-devel@nongnu.org; Fri, 16 Oct 2009 13:35:19 -0400 Received: from [199.232.76.173] (port=34526 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Myqhv-0004nR-02 for qemu-devel@nongnu.org; Fri, 16 Oct 2009 13:35:15 -0400 Received: from mx1.redhat.com ([209.132.183.28]:23751) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Myqhu-0004tJ-Jc for qemu-devel@nongnu.org; Fri, 16 Oct 2009 13:35:14 -0400 Message-ID: <4AD8AECE.9000507@redhat.com> Date: Fri, 16 Oct 2009 19:35:10 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1255037747-3340-1-git-send-email-lcapitulino@redhat.com> <1255037747-3340-2-git-send-email-lcapitulino@redhat.com> <4AD72B88.2040107@codemonkey.ws> <20091015122622.1f93ea2d@doriath> <20091015163936.GB532@redhat.com> <20091015142837.6c90580a@doriath> <4AD76B3C.3050001@codemonkey.ws> <4AD87424.3010000@redhat.com> <4AD87901.5030705@codemonkey.ws> In-Reply-To: <4AD87901.5030705@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH 01/10] Introduce qmisc module List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel@nongnu.org, Luiz Capitulino On 10/16/2009 03:45 PM, Anthony Liguori wrote: > Paolo Bonzini wrote: >> It's 36k, and pulling it in gives the opportunity to customize it. For >> example, the attached patch allows to parse a "%BLAH" extension to >> JSON that is passed to the callback (since the parsing is done >> character-by-character, the callback can consume whatever it wants >> after the % sign). Asprintf+parse JSON unfortunately isn't enough >> because you'd need to escape all strings. > > What's the state of this library's upstream? Should we be pushing these > changes there and then attempting to package it? There's no repository, there's no mention of it in the author's blog, it has seen six changes in two years according to the file's heading. The only reference on da Internet is at http://tech.groups.yahoo.com/group/json/message/928. On the other hand, it's down to the point (it has no object model of it's own), and it is fully asynchronous since it works character-by-character which makes it easier to extend as in my patch above. Paolo