On Wed, 22 Sep 2004, Dave Kuhlman wrote:

Thanks Dave,

> On Wed, Sep 22, 2004 at 03:09:01PM +0300, Toni Alatalo wrote:
> > analogous to the XML-RPC support already in Quixote" is brought up, has
> I sent Toni a copy of soapserver.py in a separate email.  (Didn't
> want to stuff mailboxes on the list with something you don't want.)
> It's a very trivial example of a SOAP server that makes several

though that did not actually address the problem I had in mind (nor was i
being explicit about, retrying now):

the nice thing for me about Quixote's XML-RPC support was that the handler
could be added just like any URL handler (i put it to /rpc/), without any
additional servers running or anything. once decided to do that, instead
of studying WSDL etc., implementing was a joy following
http://www.mems-exchange.org/software/quixote/doc/web-services.html
(started making wrapper classes that expose the actual ones of this
system, by using static methods that are passed the id of the instance
given in the xml-rpc call).

now if i indeed need SOAP, and create a separate server for it (like all
the SOAPpy examples seem to do), there needs to be some mechanism for
tying it to the system .. hm .. am using a singleton instanciated by the
Quixote Twisted publisher to access all data&functionality via http calls,
but would not be able to get that same singleton to that other process
running the SOAP server .. or could i, i.e. could it be in the same
process, would that make sense? i'm currently happy with this single
long-living process doing all the work, avoiding all concurrency issues.

if the users of the interface are ok with xml-rpc (haven't heard yet, but
am expecting a reaction today), can just thank the Quixote ppl again for
providing such a nice way for making it :)

> Dave

~Toni