From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=59027 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q4JJs-0004M7-FW for qemu-devel@nongnu.org; Mon, 28 Mar 2011 16:45:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q4JJo-0002dW-8i for qemu-devel@nongnu.org; Mon, 28 Mar 2011 16:45:45 -0400 Received: from e33.co.us.ibm.com ([32.97.110.151]:46563) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q4JJo-0002dQ-2D for qemu-devel@nongnu.org; Mon, 28 Mar 2011 16:45:44 -0400 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e33.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p2SKcwYg001472 for ; Mon, 28 Mar 2011 14:38:58 -0600 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p2SKjMKE115508 for ; Mon, 28 Mar 2011 14:45:29 -0600 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p2SKjLKS012237 for ; Mon, 28 Mar 2011 14:45:22 -0600 Message-ID: <4D90F360.3090900@us.ibm.com> Date: Mon, 28 Mar 2011 15:45:20 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [RFC][PATCH v1 05/12] qapi: fix handling for null-return async callbacks References: <1301082479-4058-1-git-send-email-mdroth@linux.vnet.ibm.com> <1301082479-4058-6-git-send-email-mdroth@linux.vnet.ibm.com> <4D8D0788.7070700@us.ibm.com> <20110328134747.5c9fbc8e@doriath> <4D90CC88.5070904@linux.vnet.ibm.com> <4D90D31F.8020405@codemonkey.ws> <4D90F2B0.908@linux.vnet.ibm.com> In-Reply-To: <4D90F2B0.908@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: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michael Roth Cc: Jes.Sorensen@redhat.com, agl@linux.vnet.ibm.com, qemu-devel@nongnu.org, Luiz Capitulino On 03/28/2011 03:42 PM, Michael Roth wrote: > > Is this supposed to be the current behavior? In early testing I > noticed that not including a tag, and issuing an async command that > never completed, still allowed for me to get responses for subsequent, > tagless/pseudo-tagged requests. I don't think the server enforces tag-reuse today as that's really something a client should be checking for. It certainly doesn't hurt for the server to complain if a client sends a tag that's already in use though. Regards, Anthony Liguori