Simon Fell > Its just code
After reading through some of the emails that Jon links to, I can see some merit in Paul Prescod's proposal that every SOAP callable method should have its own URL. This of course causes big problems for WSDL (not that problems with WSDL should be a new concept to anyone <g>)
I've just updated the round 2 interop results with the 1.3 beta 5 release of pocketSOAP.
Jon raises some interesting point on SOAP security. SOAPAction has something of a checkered past, and looks set to be deprecated in SOAP 1.2. I was against SOAPAction to start with, it seemed so pointless, its description in the spec is very vague, which i think lead to a lot of the problems. I did change my mind though, at some point there was a post from Andrew Layman (I think, it could of been Henrik Frystyk Nielsen), with a really good description of what the intent of SOAPAction was and how to use it. Unfortuantly allmost all the toolkits by default work in a manner different to this, I doubt that there are many services deployed that use SOAPAction in the intended manner.
People who are thinking about implementing the Weblogs.Com SOAP 1.1 Interface should spend a moment to think about federation. [Sam Ruby] You may also want to think about getting data out of the system in a pub/sub manner, rather than polling.