On 01/25/2011 12:14 PM, Daniel P. Berrange wrote:
It might be worth considering (the fairly newly introduced)
GVariant, rather than GValue. The GVariant code was designed
and is used for (de)serializing DBus messages in GLib. As
such I'd imagine it would be fairly well suited to handling
serializ
On Tue, Jan 25, 2011 at 11:41:23AM +0100, Paolo Bonzini wrote:
> On 01/24/2011 11:01 PM, Anthony Liguori wrote:
> >>>- JSON parser
> >>
> >>I think our JSON parser is much better than JsonGlib (which isn't
> >>anyway a part of GLib proper).
> >
> >Not sure how much either of these matter, but we sh
On 01/24/2011 11:01 PM, Anthony Liguori wrote:
- JSON parser
I think our JSON parser is much better than JsonGlib (which isn't
anyway a part of GLib proper).
Not sure how much either of these matter, but we should at least drop
QObject and convert our JSON parser to use GValues such that we c
On 01/24/2011 03:28 PM, Paolo Bonzini wrote:
On 01/24/2011 10:00 PM, Anthony Liguori wrote:
Both the recent I/O loop and threadlet series have me concerned that
we're
digging ourselves deeper into the NIH hole. I think it's time we
look at
something radical to let us borrow more code from exis
On 01/24/2011 10:00 PM, Anthony Liguori wrote:
Both the recent I/O loop and threadlet series have me concerned that we're
digging ourselves deeper into the NIH hole. I think it's time we look at
something radical to let us borrow more code from existing projects instead of
reinventing everything
