From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MzX5B-0004XC-0Y for qemu-devel@nongnu.org; Sun, 18 Oct 2009 10:50:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MzX56-0004PN-E5 for qemu-devel@nongnu.org; Sun, 18 Oct 2009 10:50:04 -0400 Received: from [199.232.76.173] (port=56807 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MzX56-0004PE-9v for qemu-devel@nongnu.org; Sun, 18 Oct 2009 10:50:00 -0400 Received: from mail-yw0-f176.google.com ([209.85.211.176]:36992) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MzX55-0002en-Gv for qemu-devel@nongnu.org; Sun, 18 Oct 2009 10:49:59 -0400 Received: by ywh6 with SMTP id 6so3014722ywh.4 for ; Sun, 18 Oct 2009 07:49:57 -0700 (PDT) Message-ID: <4ADB2B13.4090207@codemonkey.ws> Date: Sun, 18 Oct 2009 09:49:55 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH 01/10] Introduce qmisc module 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> <4AD8AECE.9000507@redhat.com> <4AD8AFA4.4070203@codemonkey.ws> <4AD8CB31.9080809@redhat.com> <4AD8E7B5.8000509@codemonkey.ws> <4AD910BA.4090607@gnu.org> <4AD922EB.5030501@codemonkey.ws> <4AD995FD.6070202@snarc.org> <20091018120631.0ab44d80@doriath> <4ADB2172.2040501@gnu.org> In-Reply-To: <4ADB2172.2040501@gnu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel@nongnu.org, Vincent Hanquez , Luiz Capitulino Paolo Bonzini wrote: > On 10/18/2009 04:06 PM, Luiz Capitulino wrote: >> Integration with QObjects is a killer feature, I think it's the >> stronger argument against grabbing one from the internet. > > Yeah, I'd say let's go with Anthony's stuff. I'll rebase the encoder > on top of it soonish (I still think it's best if JSON encoding lies in > QObject like a kind of toString). If we'll need the asynchronous > parsing later, we can easily replace it with mine or Vincent's. One thing I want to add as a feature to the 0.12 release is a nice client API. To have this, we'll need message boundary identification and a JSON encoder. I'll focus on the message boundary identification today. I'd strongly suggest making the JSON encoder live outside of QObject. There are many possible ways to represent a QObject. Think of JSON as a view of the QObject model. The human monitor mode representation is a different view. Regards, Anthony Liguori > Paolo