From: Anthony Liguori <aliguori@us.ibm.com>
To: veillard@redhat.com
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: a last comment on xml-rpc
Date: Sat, 11 Feb 2006 09:20:47 -0600 [thread overview]
Message-ID: <43EE00CF.4060607@us.ibm.com> (raw)
In-Reply-To: <20060211082102.GQ9506@redhat.com>
Daniel Veillard wrote:
> On Fri, Feb 10, 2006 at 05:38:31PM -0600, Anthony Liguori wrote:
>
>> I've also written an XML-RPC interface to Xend in C using libxml2. It
>> very little code and just works. Granted, parsing XML is more painful
>> that parsing S-Expressions but there are so many libraries for so many
>> languages that XML parsing is really a nop.
>>
>
> Did you push that code anywhere ;-) ?
>
Not yet, but I will be :-)
> I can think of 2 very different ways to do the implementation (tree + paths
> or direct SAX2 event flow) and would probably end up doing the second one
> though the code might be more complex.
I took the tree/path approach. I wrote an XML-RPC parser before using
libexpat and it was more complicated than it should have been. Once one
has a DOM structure it's a pretty straight forward recursive routine to
marshal/unmarshal.
> It might depends on the efficiency of
> the Python side, it may not be worth shaving microseconds and kilobytes
> on the C side if the Python side is one order of magnitude slower, in which
> case the simplest C code would be best.
>
Yeah, that was my basic feeling about it :-)
Regards,
Anthony Liguori
> Daniel
>
>
prev parent reply other threads:[~2006-02-11 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 22:39 a last comment on xml-rpc Ronald G Minnich
2006-02-10 23:38 ` Anthony Liguori
2006-02-10 23:40 ` Ronald G Minnich
2006-02-10 23:52 ` Matt Sottile
2006-02-10 23:49 ` Ronald G Minnich
2006-02-11 8:21 ` Daniel Veillard
2006-02-11 15:20 ` Anthony Liguori [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43EE00CF.4060607@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=veillard@redhat.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.