Re: SOAP performance data and open benchmarks

Jim Murphy wrote:
> I thought this was solved in HTTP by advertising the client's valid
> content encodings via the Accept-Encoding request header?

A well implemented server will return a 415. Unfortunately,
well-implemented HTTP servers are rare. Also, once you have had a 415,
you can resend your message but if you're smart you'll cache the fact
that that server doesn't understand encoding foo.

One problem I see here (apart from the fact that that provides a
solution only for HTTP) is that that logic is situated at a very
different place in the client than the part that receives serialisation
events to write out XML (or gzip'ed XML, or a binary infoset, etc). That
means that people (like me) wishing to provide that kind of performance
boost have much more work to do to promote interoperability. You can't
just throw in a component and expect it to work accross company
boundaries (at this point of course).

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