From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MJCMZ-0006eD-IJ for qemu-devel@nongnu.org; Tue, 23 Jun 2009 16:13:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MJCMS-0006TE-Oz for qemu-devel@nongnu.org; Tue, 23 Jun 2009 16:13:01 -0400 Received: from [199.232.76.173] (port=48654 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJCMS-0006Sl-EW for qemu-devel@nongnu.org; Tue, 23 Jun 2009 16:12:56 -0400 Received: from mx2.redhat.com ([66.187.237.31]:40431) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MJCMR-0004C9-TH for qemu-devel@nongnu.org; Tue, 23 Jun 2009 16:12:56 -0400 Message-ID: <4A41374D.2080005@redhat.com> Date: Tue, 23 Jun 2009 23:13:01 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 01/11] QMP: Introduce specification file References: <20090623012811.53a62493@doriath> <20090623144521.GA614@snarc.org> <4A40FB11.8090100@redhat.com> <4A40FB26.2040702@us.ibm.com> <4A40FD1A.1040303@redhat.com> <4A40FE31.2010007@us.ibm.com> <4A40FFB0.2070905@redhat.com> <4A411FC5.7050701@us.ibm.com> <4A412339.5000109@redhat.com> <4A412659.1080803@us.ibm.com> <4A413290.7060709@redhat.com> <4A4135ED.10908@us.ibm.com> In-Reply-To: <4A4135ED.10908@us.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: Anthony Liguori Cc: ehabkost@redhat.com, jan.kiszka@siemens.com, dlaor@redhat.com, qemu-devel@nongnu.org, Luiz Capitulino , Vincent Hanquez On 06/23/2009 11:07 PM, Anthony Liguori wrote: > Avi Kivity wrote: >> On 06/23/2009 10:00 PM, Anthony Liguori wrote: >>> For starters, there is no way to encode NULL values in a JSON >>> string. This means you cannot send binary data unless you base64 >>> encode it first. >> >> That seems to have been solved: >> >> >> js> a = 'x\0y' >> xy >> js> a.length >> 3 >> >> I don't know enough javascript to verify that it's indeed a NUL, but >> I'm guessing that it is. > > This is a browser restriction. > So this will only hit us is we port qemu to javascript and run it in a web broswer. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.