From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [RFC] Xend XML-RPC Refactoring Date: Tue, 31 Jan 2006 15:58:30 -0600 Message-ID: <43DFDD86.8080307@us.ibm.com> References: <43DFD5E6.7090909@us.ibm.com> <43DFD86B.5090900@lanl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <43DFD86B.5090900@lanl.gov> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ronald G Minnich Cc: Jeremy Katz , Matt Sottile , xen-devel , Ewan Mellor , Sean Dague List-Id: xen-devel@lists.xenproject.org Ronald G Minnich wrote: > I think moving from s-exp's to XML is a bad move. If you want, use > your s-expression library from LANL; it's used worldwide, and has done > the job for a lot of projects. Python supports XML-RPC out of the box. Using that code will remove 5k lines of code from Xend. With Python, all you have to do is register functions with the XML-RPC handler and use a proxy object. We won't have to write any XML code at all. I'm quite indifferent to XML/S-Expressions actually. It's just about simplifying things. Regards, Anthony Liguori > I know of at least one project that moved from XML to s-exp's, using > our library, because XML is just plain unwieldy. > > thanks > > ron >