From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1OANPr-00042O-2f
	for qemu-devel@nongnu.org; Fri, 07 May 2010 09:16:31 -0400
Received: from [140.186.70.92] (port=58328 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OANPn-0003vJ-3A
	for qemu-devel@nongnu.org; Fri, 07 May 2010 09:16:28 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <lcapitulino@redhat.com>) id 1OANHi-0006eL-Ap
	for qemu-devel@nongnu.org; Fri, 07 May 2010 09:08:08 -0400
Received: from mx1.redhat.com ([209.132.183.28]:14462)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <lcapitulino@redhat.com>) id 1OANHi-0006dw-3a
	for qemu-devel@nongnu.org; Fri, 07 May 2010 09:08:06 -0400
Date: Fri, 7 May 2010 10:07:58 -0300
From: Luiz Capitulino <lcapitulino@redhat.com>
Message-ID: <20100507100758.1050a374@redhat.com>
In-Reply-To: <4BE3FD3F.4070606@siemens.com>
References: <4BE3FD3F.4070606@siemens.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: Registering buffers with a qdict
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: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>

On Fri, 07 May 2010 13:45:03 +0200
Jan Kiszka <jan.kiszka@siemens.com> wrote:

> Hi Luiz,
> 
> what is the recommended way of pushing larger buffers (up to 64K so far)
> into a qdict? QLIST of QINT (one per byte) looks a bit heavy. I thought
> about hex-encoding the content first (series of "%02X"), then
> registering it as QSTRING. Or should we introduce a new type, QBUFFER?

 I don't think that hex-encoding the contents is so bad if your use case is
very specific and isolated.

 On the other hand, I do prefer a QBuffer type, specially because we can
have buffer operations.