On Mon, 10 May 2010 12:59:47 +0200
Jan Kiszka jan.kis...@siemens.com wrote:
Luiz Capitulino wrote:
On Fri, 07 May 2010 16:21:13 +0200
Jan Kiszka jan.kis...@siemens.com wrote:
Luiz Capitulino wrote:
On Fri, 07 May 2010 13:45:03 +0200
Jan Kiszka jan.kis...@siemens.com wrote:
Hi
On 05/10/2010 01:59 PM, Jan Kiszka wrote:
From a quick glance at the JSON spec, there is no room for a new type. I
think we have to overload an existing one and convert that into a
QBuffer (typically, we know the actual semantic). Hex string encoding is
most compact, so I went this road.
Avi Kivity wrote:
On 05/10/2010 01:59 PM, Jan Kiszka wrote:
From a quick glance at the JSON spec, there is no room for a new type. I
think we have to overload an existing one and convert that into a
QBuffer (typically, we know the actual semantic). Hex string encoding is
most compact, so I
On 05/10/2010 04:43 PM, Jan Kiszka wrote:
Avi Kivity wrote:
On 05/10/2010 01:59 PM, Jan Kiszka wrote:
From a quick glance at the JSON spec, there is no room for a new type. I
think we have to overload an existing one and convert that into a
QBuffer (typically, we know the actual
On Fri, 07 May 2010 13:45:03 +0200
Jan Kiszka jan.kis...@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
Luiz Capitulino wrote:
On Fri, 07 May 2010 13:45:03 +0200
Jan Kiszka jan.kis...@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
On Fri, 07 May 2010 16:21:13 +0200
Jan Kiszka jan.kis...@siemens.com wrote:
Luiz Capitulino wrote:
On Fri, 07 May 2010 13:45:03 +0200
Jan Kiszka jan.kis...@siemens.com wrote:
Hi Luiz,
what is the recommended way of pushing larger buffers (up to 64K so far)
into a qdict? QLIST of
