Hi There,
On 05/01/12 18:14, Wolfgang Sourdeau wrote:
Hi Burak!
Regarding the fact that you removed the script, please note that
except of generating the code automatically, this has just the effect
of forcing the developer to do it manually. So as long as the wsdl
"class builder" is not in place, it's a bit useless since the effect
is the same...
If you need a soap client, just use suds. Rpclib's client functionality
could be preferred only when:
1) You need faster xml parsing.
2) You can import server code from client. (Yes, that means you're
making calls to an rpclib server)
(If speed is a concern, you shouldn't be using soap anyway, but that's
another matter)
I also wanted to focus on making soaplib a proper soap server,
because that's what was lacking then in the Python world. (There even
was a time i'd entirely dumped client functionality in favor of
suds.) Oh and wsdlparse did not work most of the time anyway.
If suds wasn't already there, we'd probably have wsdl parsing in
rpclib by now. (I already have a javascript soap client which also
parses wsdl, here: http://github.com/arskom/qxsoap) But I did not
think duplicating suds' functionality in rpclib would benefit
anybody, so I didn't do it.
What do you mean by the "suds functionality" ? The fact that it's a
client interface library?
I mean I did not implement wsdl parsing in rpclib because suds already
had it. if you dig up the archives of this mailing list from 2010-11ish,
you'll see the discussions.
best,
burak
_______________________________________________
Soap mailing list
[email protected]
http://mail.python.org/mailman/listinfo/soap
