On 10/24/06, <b class="gmail_sendername">Arwyn Hainsworth</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div>As for inventing protocols, that depends. One way of doing it is to use the http/tls python libraries to create a specialised mini-webserver that serves and receives XML (SOAP?) files. That way various back ends can be implemented.
<br><br>I'm a bit busy these coming few weeks, so I can't sit down and write a full spec, only assist, but If no one has done it by the time I'm free, I'll write one.<br></div><span class="sg"></span></div></blockquote></div>
<br>I collaborated for some time with CherryPy (about two years ago), and wrote some of the XMLRPC code back then. It makes sense, it's possible to implement a complete API to edit/maintain the server configuration. CherryPy it's very simple, and it's quite easy to put it to work with HTTPS (it now supports WSGI, the new Python spec for Web applications; also, stunnel or something similar can be used).
<br><br>-- <br>Carlos Ribeiro<br>Consultoria em Projetos<br>blog: <a href="http://rascunhosrotos.blogspot.com">http://rascunhosrotos.blogspot.com</a><br>blog: <a href="http://pythonnotes.blogspot.com">http://pythonnotes.blogspot.com
</a><br>mail: <a href="mailto:email@example.com">firstname.lastname@example.org</a><br>mail: <a href="mailto:email@example.com">firstname.lastname@example.org</a><br><br>