Hi Christophe, Thank you very much for responding.
On 12/08/11 13:37, Christophe de Vienne wrote: > Hello, > > I am the author of http://packages.python.org/WSME/. > > The original goal of this project is to write a better TGWebServices, > while keeping a very similar (if not identical) API. > The "better" things I needed were : > > * Batch calls (for the ExtDirect implementation which is the one I > am using the most the this time, and also for json-rpc which will > come sooner or later). > How do you support batching with soap? Soap the protocol does not support batching as far as i know. (i.e. soap:Body has max_occurs=1 in the soap 1.1 schema) > * Extendible type system > can you elaborate on that? both rpclib and ladon support extensible types one way or the other. > * Take the protocol implementations out of the core API so that they > can be safely tweaked > again, these are one of the major features of both rpclib and ladon. or am i misunderstanding something? > * Portability to TG2 without rewriting everything like I had to do > for http://pypi.python.org/pypi/TGWebServices/2.0.0a2 > I can't comment on this as i'm not familiar with turbogears. here's a django wrapper for rpclib: https://gist.github.com/1242760 Would writing a tg wrapper be much more work than this? > The bonus of this rewrite was to remove completely the TG requirement. > > Note that only a subset of each protocol is generally implemented, the > one that is necessary to expose the API. > Oh especially with soap, that's how it works almost everywhere :) Best, Burak
_______________________________________________ Soap mailing list [email protected] http://mail.python.org/mailman/listinfo/soap
