5230Re: [decentralization] Re: xml protocols and transport bindings
- Feb 3, 2002allenjswa wrote:
>Different clients and servers generate different versions of namespace
> > sufficient trouble with simple SOAP over HTTP that I haven't even
> > able ot try it.
> What have you had trouble with?
For example: http://schemas.xmlsoap.org/soap/envelope/ versus
And of course encoding and schema namespaces have also changed.
Null/nil handing is not compatible depending on what version of SOAP the
There are a variety of conventions for SOAPAction.
Some implementations don't handle complex types.
At least one implementation doesn't handle namespaces correctly.
> ... I have never *not* had SOAP workI guess we have had different experiences. Time will tell.
> when I tried to call various methods at XMethods or web services I
> develop myself.
>...If SOAP is a message format, then why does it need complex data
> You already have the answer. It's a message format that can be used
> (and is used) in things like "dcom for the web" and "asynchronous
> rpc". You can confuse yourself if you want, but it is not that
structuring conventions? Wouldn't a message format usually leave that in
the domain of the application? Also, if it is a *format* then why does
it need to have anything to say about whether it is used for RPC or
asynch or ... usually the message pattern is the domain of the protocol,
not the format. Most of that stuff has been moved to a separate
specification from the envelope part so there are moves towards
rationality. Maybe the non-envelope bits could also be renamed.
- << Previous post in topic Next post in topic >>