From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MqWbC-0007VA-Sk
	for qemu-devel@nongnu.org; Wed, 23 Sep 2009 14:29:54 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MqWb7-0007Uy-Eo
	for qemu-devel@nongnu.org; Wed, 23 Sep 2009 14:29:53 -0400
Received: from [199.232.76.173] (port=57905 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MqWb7-0007Uv-Ab
	for qemu-devel@nongnu.org; Wed, 23 Sep 2009 14:29:49 -0400
Received: from mail-qy0-f173.google.com ([209.85.221.173]:60931)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1MqWb7-000332-27
	for qemu-devel@nongnu.org; Wed, 23 Sep 2009 14:29:49 -0400
Received: by qyk3 with SMTP id 3so832048qyk.4
	for <qemu-devel@nongnu.org>; Wed, 23 Sep 2009 11:29:48 -0700 (PDT)
Message-ID: <4ABA6741.2020903@codemonkey.ws>
Date: Wed, 23 Sep 2009 13:21:53 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] ANN: QEMU Monitor Protocol git tree
References: <20090921224430.610da97b@doriath>	<4AB98034.3060608@codemonkey.ws>
	<20090923111824.6a48bec4@doriath>
In-Reply-To: <20090923111824.6a48bec4@doriath>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org, avi@redhat.com

Luiz Capitulino wrote:
>  Hm, I've assumed some kind of end of line would be needed.

We'll definitely do some sort of pretty printing but from a protocol 
definition perspective, I think it's good for us to not guarantee 
whitespace as a boundary separator.  I think it just suggests that we 
need a streaming json parser.

>  I thought that clients would always want to know to what
> QEMU they are talking to.
>   

They definitely do but we can use a command to figure that out (like 
info version).

It's good to avoid putting too much in the initial hello because it's 
the only thing that can never change based on capabilities.

Regards,

Anthony Liguori

>  What do you suggest?
>