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.
Base64 is even more compact.
But I'm open to change it into a true type if JSON actually allows it (or we are fine with breaking it).
That ruins any possibility of using a standard json encoder/decoder on the other end.
-- error compiling committee.c: too many arguments to function
