Re: customized encoding and SOAP interoperability

Jim Murphy wrote:
>>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
>
> I think you're giving clients too much credit.  Have you tested this
> elegant fallback/doengrade with mainstream SOAP client toolkits?

I think SOAP::Lite is the one that initiated the idea, last time I
checked it was the only one that did that. I was hoping that Axis would
do that as well but it would seem that sending anything other than raw
UTF-8 XML was never taken into consideration there.

--
Robin Berjon <[email protected]>
Research Engineer, Expway
7FC0 6F5F D864 EFB8 08CE  8E74 58E6 D5DB 4889 2488

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