Re: customized encoding and SOAP interoperability

. 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

Yes - I probably am :) Additionally, this fallback mechanism is only for
HTTP.

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

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