Re: customized encoding and SOAP interoperability

> [mailto:[email protected]] On Behalf Of Neela Lakshminarayan
> Sent: Thursday, November 14, 2002 9:24 PM

> > Customized encoding means you have compromised SOAP
interoperability.
> > Is there any reason not to expect so?
>
> No - there's no reason not to expect so. I was wondering how big a
price
> we are paying for making this compromise.
> As far as I can tell - it is probably one additional round trip. i.e
our
> client may send a customized encoding to a server that may not
understand
> this encoding. The server will hopefully return a HTTP 415 error. The
> client will then send uncompressed content.
> The client will also learn the fact that this server does not
understand
> this encoding and will not send customized encoded content to this
server
> in the future.

I think you're giving clients too much credit.  Have you tested this
elegant fallback/doengrade with mainstream SOAP client toolkits?

Jim

You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other
DevelopMentor lists at http://discuss.develop.com.