From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=45703 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Q4Hkq-0004l4-ML
	for qemu-devel@nongnu.org; Mon, 28 Mar 2011 15:05:33 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Q4Hkp-00023b-AR
	for qemu-devel@nongnu.org; Mon, 28 Mar 2011 15:05:32 -0400
Received: from mail-iw0-f173.google.com ([209.85.214.173]:64720)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1Q4Hkp-00023V-69
	for qemu-devel@nongnu.org; Mon, 28 Mar 2011 15:05:31 -0400
Received: by iwl42 with SMTP id 42so4700788iwl.4
	for <qemu-devel@nongnu.org>; Mon, 28 Mar 2011 12:05:30 -0700 (PDT)
Message-ID: <4D90DBF9.2050700@codemonkey.ws>
Date: Mon, 28 Mar 2011 14:05:29 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [RFC][PATCH v1 07/12] qmp proxy: core code for
	proxying qmp requests to guest
References: <1301082479-4058-1-git-send-email-mdroth@linux.vnet.ibm.com>	<1301082479-4058-8-git-send-email-mdroth@linux.vnet.ibm.com>	<4D8D08DE.8050805@us.ibm.com>
	<4D8D0F79.6030005@linux.vnet.ibm.com>
In-Reply-To: <4D8D0F79.6030005@linux.vnet.ibm.com>
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.nongnu.org/archive/html/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: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: aliguori@linux.vnet.ibm.com, Anthony Liguori <aliguori@us.ibm.com>, agl@linux.vnet.ibm.com, qemu-devel@nongnu.org, Jes.Sorensen@redhat.com

On 03/25/2011 04:56 PM, Michael Roth wrote:
>> I don't quite follow what this is doing.
>>
>
>
> That's for the session negotiation so we can reset state when the 
> guest agent restarts. The sequence is:
>
> guest -> host
> { "_xport_event": "guest_init", "_xport_arg_sid": <random session id> }
>
> host -> guest
> { "_xport_event": "host_ack", "_xport_arg_sid": <received session id> }
>
> Guest will ignore anything it gets until it sees an ack with the 
> proper session id, host will cancel outstanding requests when it 
> receives a guest init. If there's already an event waiting to be sent 
> we clobber it since for the above exchange only the most recent event 
> we sent matters.
>
> We send them as json objects, but they get handled at transport level 
> and terminate there.

Doesn't an invalid UTF-8 sequence provide the same functionality?

Regards,

Anthony Liguori