From: Rich S. <rs...@zo...> - 2001-09-05 00:45:50
|
Paul Prescod wrote: > > It would be great if I could also do this: > > #!/usr/bin/env python2.1 > import zsiserver > ...various functions > > zsiserver.server_forever() Sure. You'll need at least one parameter, the URL, and I'd want to let you do a whole bunch of registers (possibly with namespace) and then a serve_forever ... But that basic thing is no problem. I assume you don't care if it's built on python's httpserver. > > The input arg will be a possibly-empty > > dictionary; > > I think there is a problem here. Some SOAP implementations generate > bogus names (typically gensym) and depend instead on the *order* of > parameters. But wrapping them in a dictionary loses order. Somewhat flip answer: without external schema information you don't know that the order matters. If you do know that the order matters, then do it Right (sic :) and use typecodes. Real answer: SOAP encoding says that within a struct order does not matter, only names. So if there's an implementation that is using gensym'd names (I use id() myself) and requiring its recipients to know the order, that implementation is wrong. Order *does* matter for arrays, of course, and ZSI does them as python lists. /r$ -- Zolera Systems, Securing web services (XML, SOAP, Signatures, Encryption) http://www.zolera.com |