All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ronald G Minnich <rminnich@lanl.gov>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Jeremy Katz <katzj@redhat.com>, Matt Sottile <matt@lanl.gov>,
	xen-devel <xen-devel@lists.xensource.com>,
	Ewan Mellor <ewan@xensource.com>, Sean Dague <japh@us.ibm.com>
Subject: Re: [RFC] Xend XML-RPC Refactoring
Date: Tue, 31 Jan 2006 14:36:43 -0700	[thread overview]
Message-ID: <43DFD86B.5090900@lanl.gov> (raw)
In-Reply-To: <43DFD5E6.7090909@us.ibm.com>

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

  reply	other threads:[~2006-01-31 21:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31 21:25 [RFC] Xend XML-RPC Refactoring Anthony Liguori
2006-01-31 21:36 ` Ronald G Minnich [this message]
2006-01-31 21:47   ` Matt Sottile
2006-01-31 21:58   ` Anthony Liguori
2006-02-01  9:53   ` Ewan Mellor
2006-02-01  9:37 ` Daniel Veillard
  -- strict thread matches above, loose matches on Subject: below --
2006-03-07 23:37 Ian Pratt
2006-03-08  0:07 ` Anthony Liguori
2006-03-11 20:55   ` Ewan Mellor
2006-03-11 21:36     ` Daniel Veillard
2006-03-11 22:20       ` Ewan Mellor
2006-03-12  1:46         ` Anthony Liguori
2006-03-12  9:27           ` Daniel Veillard
2006-03-12  9:57         ` Daniel Veillard
2006-03-12 17:41           ` Anthony Liguori
2006-03-12  1:44     ` Anthony Liguori
2006-03-13 10:30       ` Ewan Mellor
2006-03-14  6:58     ` Anthony Liguori
2006-03-14  8:35       ` Ewan Mellor

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=43DFD86B.5090900@lanl.gov \
    --to=rminnich@lanl.gov \
    --cc=aliguori@us.ibm.com \
    --cc=ewan@xensource.com \
    --cc=japh@us.ibm.com \
    --cc=katzj@redhat.com \
    --cc=matt@lanl.gov \
    --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.