Can someone describe what the "slow part of web services is"? If you think its the verbosity of XML I suspect your not measuring it against alternatives. The fact is unless your message payload is very large the size of the XML body matters little in your overall performance - over broadband.

A great example of this is trying to optimize SOAP envelopes in the < 1500 byte range - where many SOAP envelopes fall. In this common case the ethernet frame size is packed up to ~1500 when you don't use all ~1500 so "optimizing" from 1000 bytes to 500 just costs you. Its costs you the time and complexity of the compression step.

When message sizes get larger it's still not the perf killer you may think - until messages sizes exceed !MB - YMMV.

Jim Murphy
Mindreef, Inc.


[EMAIL PROTECTED] wrote:

  I read an article about Fast Web Services... but I think there was no
new development since then.

http://java.sun.com/developer/technicalArticles/WebServices/fastWS/



Thank you for the responses.  I think it's possible to achieve
interoperability and small foot print.  It's just Soap was designed
lousy in this particular aspect.  When saying if speed matters, I think
most of the apps that has some kind of communication, speed does
matter.  I think there should be a new standard/version to replace Soap
if this cannot be addressed.

Paul Callahan wrote:


I second that...  And would just add that you might want to think about
when your application is just too 'chatty' for SOAP...

-pc

On Tue, 16 Nov 2004 08:48:30 -0900, Elaine Nance
<[EMAIL PROTECTED]> wrote:



SOAP is not designed to create compact dataflows.  It is designed for
interoperability and, because it is XML, extensibility.
IMHO, I would *not* use SOAP for purely internal processes if
speed or stream size matters (where faster/smaller) is better.

In that case I would go strictly with a socket-level approach.

Just my 2 small coins,
Elaine



Vy Ho wrote:



I look at a message send back from the server to a client in Axis,
and was very surprised that most of the text is not the data that I
need to send, but declaration and long namspaces.  Is it possible to
reduce these down and still comply with Soap?

Thanks,

vh




<~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Computers are useless. They can only give you answers. | -- Pablo Picasso -- <~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~









Reply via email to