Re: customized encoding and SOAP interoperability

Customized encoding means you have compromised SOAP interoperability.
Is there any reason not to expect so? To foster interoperability you
may document well your encoding methods, have readily available
implementation
and be ready to share it with business partners.

Soumen Sarkar.

-----Original Message-----
From: Neela Lakshminarayan [mailto:[email protected]]
Sent: Thursday, November 14, 2002 4:44 AM
To: [email protected]
Subject: [SOAP] customized encoding and SOAP interoperability


We have a client communitcating with a Java Servlet through SOAP messages.
The SOAP implementation is our own but it does conform to the SOAP
specification. Since our response can be very verbose, we decided to
compress our messages. For certain reasons, we are unable to use the
standard encoding methods such as gZip, deflate, compress etc. We have a
customized encoding. We don't like deviating from standards but in this case
we had to.

My question is - by using a customized encoding, have we terribly
compromised SOAP interoperability? Is customized encoding a terrible thing
to do?

Currently we don't care about being interoperable with other SOAP toolkits -
but the requirement might change in the future.

Thanks,
Neela

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.