Re: [Xen-devel] [PATCH V4] libxl, Introduce a QMP client

I wrote:
> Oh wait, I just looked up yajl.  Why are we using a SAX-style
> (callback-based) json parser ?
> 
> Surely it would be better to use a json library which simply provides
> an in-memory data structure for each json object.  We don't anticipate
> dealing with any huge json objects (which is the motivation for the
> SAX-style approach).

Well, I went and did some searching and I have discovered that:

There does not appear to be any widely-used "atomic-style" json
library for C, other than the one which comes with glib (which is
unsuitable because we don't want to import glib into our project).

YAJL 2 does have a simple "atomic" ("tree" they call it) interface.
It's not in squeeze or afaict recent fedora.

YAJL 1 is even lacking in Debian lenny.  :-/.

So probably what we have is the best approach.  But perhaps it might
be worth considering whether we should make our interface to json
objects the similar to yajl 1's tree interface ?

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

[Xen-devel] [PATCH 5 of 5] xenctx: dump pagetable, Olaf Hering

Next by Date:

Re: [Xen-devel] [PATCH 1 of 1] xen-backwatch: Deal with broken frontend/backend ring I/O, Ian Jackson

Previous by Thread:

Re: [Xen-devel] [PATCH V4] libxl, Introduce a QMP client, Ian Jackson

Next by Thread:

Re: [Xen-devel] [PATCH V4] libxl, Introduce a QMP client, Ian Campbell

Indexes:

[Date] [Thread] [Top] [All Lists]