From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ronald G Minnich Subject: Re: [RFC] Xend XML-RPC Refactoring Date: Tue, 31 Jan 2006 14:36:43 -0700 Message-ID: <43DFD86B.5090900@lanl.gov> References: <43DFD5E6.7090909@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <43DFD5E6.7090909@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: Jeremy Katz , Matt Sottile , xen-devel , Ewan Mellor , Sean Dague List-Id: xen-devel@lists.xenproject.org Anthony Liguori wrote: > Hi, > > I wanted to give the list a heads up about something a number of us > discussed at the recent XenSummit. > > We would like to simplify Xend by utilizing more of the standard Python > library and relying on less of our own code. The most obvious thing > here is the current S-Expression/HTTP RPC interface. We would like to > replace this with XML-RPC using Python's builtin support (xmlrpclib and > SimpleXMLRPCServer). > > I've got some initial code and more details on the wiki > (http://wiki.xensource.com/xenwiki/Xend/XML-RPC). Early estimates are > that this would reduce the code in Xend by about 33% (5k slocs). We > would also like to standardize this XML-RPC interface so that > third-parties write apps to this interface without worrying about > massive breakage. 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. 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