Re: SOAP performance data and open benchmarks

Neelakantan Lakshminarayan wrote:
> What exactly is the issue with compression and interoperability? If the
> compression algorithms are well known - gzip for example - is there still an
> issue? I'm trying to understand what it is that we lose if chose to compress
> SOAP messages.

If the other end doesn't support the compression your are using -- well
known or not -- then you lose interoperability. That's a problem I am
currently facing as I am working on a prototype to provide binary XML
serialisation (with much smaller messages and much faster parsing) for
SOAP.

Issues of making it available to all implementations are solvable with
pluggable components such as JAX-RPC's XMLWriter and XMLReader (I wish
all Java implementations supported that, and better that implementations
in other languages had similar common interfaces -- it makes a lot of
sense wrt the SOAP spec).

However issues of "how to know that you can use that with the other end"
are much harder. Restricting yourself to the HTTP binding, you can rely
on the same approach that SOAP::Lite does which is to test for a 415
error, but that's not very pleasant. I guess that might be a candidate
for something that is to be specified at a higher level.

--
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.