<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Tristan Seligmann wrote:
<blockquote cite="mid20060410110743.GB25250@mithrandi.za.net"
type="cite">
<pre wrap="">
I would recommend transferring plain custom XML documents over HTTP,
rather than introducing an extra layer of pain with SOAP or XML-RPC.
</pre>
<blockquote type="cite">
<pre wrap="">Also, it would be nice if I could use any transport mechanism to send
the commands. eg. http, https, ssh, rsh. Can Twisted be used to
provide such a generic transport mechanism? If not would, SOAP or
XMLRPC be better choices, or is the question of transport irrelevant.
</pre>
</blockquote>
<pre wrap=""><!---->
I believe SOAP and XML-RPC are only defined over HTTP (including https,
because that's more or less an extra layer underneath it). I'm not sure
there's any value in transmitting SOAP/XML-RPC XML documents over
something like ssh.
</pre>
</blockquote>
For a more formal approach to "XML documents over HTTP" doing in a sane
fashion what SOAP/XML-RPC wants to achieve:<br>
<br>
<a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/Representational_State_Transfer">http://en.wikipedia.org/wiki/Representational_State_Transfer</a><br>
<br>
With Twisted you can easily roll your own RESTive interface.<br>
<br>
regards,<br>
<br>
Eugene Coetzee<br>
<br>
</body>
</html>