Re: [Pywebsvcs-talk] Re: [XML-SIG] SOAP in CGI-like environments

[Rich S. <rs...@zo...>]

> Sec 7 says model it as a struct with parameters in the order of the
> function signature, but if you use sec5 encoding, you're entitled to
> serialize them in aribtrary order.
> 
> But it does appear that the spec is inconsistent here, so I'll ask on
> the soapbuilders mailing list.

I did ask, and one person responded that the pragmatic thing to do is
turn off ordering.

> In order to get something out there, I'm willing to implement
> dispatch/invocation of something, ideally interoperable.  Since there is
> no requirement that parameters names match, I'm inclined to implement
> the nameless order-preserving.

And that is what I did.

> > $server = SOAP::Lite
> >         ->uri($ns)
> >         -> proxy($server_url);
> >
> > print $server-> f2c(70, 90)
> >         -> result;

s = SOAPIO('host:port', '/cgi-bin/dispatch')
print s.echo(1,2,3)
print s.foo('hello', 'world')
print s.echo('hello mom')

you can also get a "bound function"
	f = SOAPIO('host:post', '/some/uri', ssl=1).Delete
	f('/dev/null')
	f('c:/autoexec.bat')
etc.

There are also "modifiers" so you can do things like
	s.SetAuth(AUTH.httpbasic, 'myname', 'mypass').foo('bar')

It's built on top of httplib, so SSL is supported where available, but
proxies are not supported.
	/r$