From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MKyHK-0002hL-9J
	for qemu-devel@nongnu.org; Sun, 28 Jun 2009 13:34:58 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MKyHF-0002g4-OZ
	for qemu-devel@nongnu.org; Sun, 28 Jun 2009 13:34:58 -0400
Received: from [199.232.76.173] (port=60818 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MKyHF-0002fz-Kz
	for qemu-devel@nongnu.org; Sun, 28 Jun 2009 13:34:53 -0400
Received: from mx2.redhat.com ([66.187.237.31]:57095)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1MKyHF-0007w9-5m
	for qemu-devel@nongnu.org; Sun, 28 Jun 2009 13:34:53 -0400
Message-ID: <4A47AA10.10106@redhat.com>
Date: Sun, 28 Jun 2009 20:36:16 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 01/11] QMP: Introduce specification file
References: <4A412339.5000109@redhat.com> <4A4395B8.4010401@redhat.com>	
	<4A43BD5D.80307@codemonkey.ws> <4A43C264.6060803@redhat.com>	
	<4A43D600.8060605@codemonkey.ws> <4A449113.8070907@redhat.com>	
	<4A44CB74.1070808@codemonkey.ws> <4A44E2F3.8050804@codemonkey.ws>	
	<5b31733c0906261036o272bcd8xffc0f2e209b778a5@mail.gmail.com>	
	<4A45232F.50306@codemonkey.ws>
	<5b31733c0906261325ye5fe937wea277c2d87ccd1e1@mail.gmail.com>
	<4A476D46.2000909@redhat.com> <4A47A8AF.3030905@codemonkey.ws>
In-Reply-To: <4A47A8AF.3030905@codemonkey.ws>
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: Anthony Liguori <anthony@codemonkey.ws>
Cc: "ehabkost@redhat.com" <ehabkost@redhat.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>, "jan.kiszka@siemens.com" <jan.kiszka@siemens.com>, "dlaor@redhat.com" <dlaor@redhat.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, Luiz Capitulino <lcapitulino@redhat.com>, Filip Navara <filip.navara@gmail.com>, Vincent Hanquez <tab@snarc.org>

On 06/28/2009 08:30 PM, Anthony Liguori wrote:
>> Another candidate is screendump.  There's no reason to go through a 
>> file.  We could pass a pipe as an fd and request a screendump to that 
>> fd, but that's rather roundabout.
>
>
> Instead of inventing binary syntaxes, maybe we could use dictionary 
> syntax to denote a mime encoded value?
>
> So something like:
>
> {"Content-Type": "image/ppm", "Content-Transfer-Encoding": "base64", 
> "Content": "AB234SDFSDf=="}
>
> A special brace format could be used if we wanted to make sure it was 
> independently parsable:
>
> <"Content-Type": "image/ppm", "Content-Transfer-Encoding": "base64", 
> "Content": "AB234SDFSDf==">
>
> But I suspect dicts are good enough.

Yes.

(I see a future thread about how we negotiate content types etc.)

-- 
error compiling committee.c: too many arguments to function