SOAPpy is a very primitive soap implementation compared to ZSI, but it works for the simple cases. However, focus is being directed to ZSI primarily now. If you check out ZSI from cvs you can build it with, "python setup.py build --twisted", and this will include twisted resources that can be used like any other twisted.web resource. This work migrated from pygridware to ZSI recently, so it is not trivial to use yet. Pygridware also includes a web2 resource, but this has not been moved to ZSI yet. Maybe once these classes mature they will be donated for twisted to include. I am not a twisted developer so I can't speak for them, but this is the current status of the pywebsvcs group. I cc'd the twisted-web mailing list, because that is probably where this thread belongs, hence the general list should not be included in future replies.
On 2/28/06, Richard Townsend email@example.com wrote:
I've been experimenting with the Twisted web/soap.py integration with SOAPpy which appears to do the sort of I stuff I need at the moment.
However, a recent message on the Pywebsvcs-talk mailing list said:
"Any objection to our diabolical plan to integrate wstools into ZSI and shove SOAPpy to a second class status? We'd like to converge on a single python web services solution, but we're working hard to make sure SOAPpy users can do in ZSI what they can do in SOAPpy..."
What effect will this development have on support for SOAP in Twisted?
Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python