From: Ronald G Minnich <rminnich@lanl.gov>
To: xen-devel <xen-devel@lists.xensource.com>, Matt Sottile <matt@lanl.gov>
Subject: a last comment on xml-rpc
Date: Fri, 10 Feb 2006 15:39:17 -0700 [thread overview]
Message-ID: <43ED1615.7030209@lanl.gov> (raw)
we get this kind of note all the time, and just got another one.
Chessbrain II, which used to use XML-RPC, has moved to Matt's
s-expression library. For more on chessbrain:
"It is being used in two projects, msgCourier (an open source messaging
server) and on the ChessBrain project. ChessBrain is a distributed
computing project (similar to SETI@home) that plays the game of chess
using thousands of computers. ChessBrain was awarded a 2005 Guinness
World Record involving distributed computation (see
http://www.chessbrain.net and http://www.msgcourier.com). The new
ChessBrain II (which has been in development for two years now) will
utilize msgCourier during its next world record attempt in Copenhagen.
The underlying communication protocol will use s-expr and Matt's sfsexp."
I think Xen made the right decision, in the beginning, to use s-exprs.
We have heard from any number of places that learned the hard way that
XML is a really poor foundation for RPC.
I hope you will reconsider going to XML-RPC. I don't think the existence
of python support is sufficient. The whole point of RPC, in fact, is to
let any client talk to any server, without regard to language or
environment. We know in practice that trivial C programs can use
s-expression based RPC; we've seen how awful the XML parsers in C can
be; do you really want to lock C out of this picture?
thanks
ron
next reply other threads:[~2006-02-10 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 22:39 Ronald G Minnich [this message]
2006-02-10 23:38 ` a last comment on xml-rpc Anthony Liguori
2006-02-10 23:40 ` Ronald G Minnich
2006-02-10 23:52 ` Matt Sottile
2006-02-10 23:49 ` Ronald G Minnich
2006-02-11 8:21 ` Daniel Veillard
2006-02-11 15:20 ` 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=43ED1615.7030209@lanl.gov \
--to=rminnich@lanl.gov \
--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.