From: Anthony Liguori <aliguori@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Cc: Ewan Mellor <ewan@xensource.com>
Subject: [PATCH 0/3] Add XML-RPC support to Xend
Date: Tue, 28 Feb 2006 16:22:02 -0600 [thread overview]
Message-ID: <4404CD0A.6000903@us.ibm.com> (raw)
The following patches implement XML-RPC for Xend. The first patch just
adds a new server for Xend that exposes the same functions exposed by
the S-Expression/HTTP server expect by XML-RPC. There is no change to
the code paths taken for any xm commands so it's a rather safe patch to
include.
The second patch changes XendClient to use XML-RPC and makes a few
subsequent changes to xm to know about the new exception types
generated. This changeset has been passing xm-test for the past couple
weeks so I'm rather confident that it doesn't introduce any major
regressions.
One thing to notice (from the attached diffstat output) is that there is
a net reduction in SLOCs even though no functionality was removed.
This is because XendClient was greatly simplified by using XML-RPC.
b/tools/python/xen/util/xmlrpclib2.py | 109 +++++++
b/tools/python/xen/xend/server/XMLRPCServer.py | 97 ++++++
tools/python/xen/xend/XendClient.py | 369 +++----------------------
tools/python/xen/xend/XendDomain.py | 2
tools/python/xen/xend/server/SrvServer.py | 2
tools/python/xen/xm/create.py | 8
tools/python/xen/xm/main.py | 26 -
7 files changed, 270 insertions(+), 343 deletions(-)
Regards,
Anthony Liguori
next reply other threads:[~2006-02-28 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 22:22 Anthony Liguori [this message]
2006-02-28 22:23 ` [PATCH 1/3] Add XML-RPC support to Xend Anthony Liguori
2006-02-28 22:24 ` [PATCH 2/2] " Anthony Liguori
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=4404CD0A.6000903@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=ewan@xensource.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.