From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Veillard Subject: Re: a last comment on xml-rpc Date: Sat, 11 Feb 2006 03:21:02 -0500 Message-ID: <20060211082102.GQ9506@redhat.com> References: <43ED1615.7030209@lanl.gov> <43ED23F7.7040300@us.ibm.com> Reply-To: veillard@redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <43ED23F7.7040300@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Anthony Liguori Cc: Matt Sottile , xen-devel , Ronald G Minnich List-Id: xen-devel@lists.xenproject.org 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 ;-) ? 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. 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. Daniel -- Daniel Veillard | Red Hat http://redhat.com/ veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/