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.
9 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Signal to noise ratio in Soap is very high
>
>
> Thank you for the link. Apache Tomcat already support server side gzip
> compression. I only need to do this on the client side. There's also
> free source code for doing the serv
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
Thank you for the link. Apache Tomcat already support server side gzip
compression. I only need to do this on the client side. There's also
free source code for doing the servlet that does the compression (very
straight forward, because java already supply the gzip compression
stream library
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 shou
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
Check http://www.osmoticweb.com/soap-compression-howto.htm
Christophe
> -Original Message-
> From: Vy Ho [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 16, 2004 12:11 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Signal to noise ratio in Soap is very high
>
>
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 sock
Searching around, I found this article:
http://www-106.ibm.com/developerworks/webservices/library/ws-sqzsoap.html#code2
This basically add gzip to both end of the connection so that things
gets smaller in the stream.
The concept seems to be good. Is something Axis already implemented, so
that I
What I meant is the signal to noise ratio is very low.
10 matches
Mail list logo
