You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by David Kerber <dc...@verizon.net> on 2006/03/15 22:54:28 UTC
How to reduce bandwidth (meaning message size) with Axis
Are there any adjustments I can do to my Axis settings to reduce the
bandwidth usage on my SOAP requests? In particular, I would like to
know how I can get rid of the
"xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"" items in the
argument elements. I'm using the minimum call settings, letting handle
as much of it as possible automatically. If I need to set some
parameters in code, that's fine, but please tell me which ones. My full
SOAP request for a test run is below.
The reason this is an issue is that this is an automated data collection
system working over a WAN. Right now, we get about 800,000 data records
per day, and are only about 20% deployed for one customer. BW is going
to be a significant issue as we continue to roll this out.
Thanks!
Dave
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<ns1:getDataLine
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns1="http://localhost:8081/axis/EddService.jws">
<ns1:arg0 xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
1234501
</ns1:arg0>
<ns1:arg1 xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
2/2/2
</ns1:arg1>
<ns1:arg2 xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
Wed Mar 15 16:44:57 EST 2006
</ns1:arg2>
<ns1:arg3 xsi:type="soapenc:string"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
This is the data line
</ns1:arg3>
</ns1:getDataLine>
</soapenv:Body>
</soapenv:Envelope>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: How to reduce bandwidth (meaning message size) with Axis
Posted by Jon Wingfield <jo...@mkodo.com>.
Compression works very well.
I added a homegrown GZip filter to the AXIS urls and also saw approx 10x
compression. There are also a number of similar OSS Filters out there.
There were .NET clients accessing the web-services and they needed a
tweak to handle the compression:
http://www.dotnetjunkies.com/Tutorial/90D3B3E0-6544-4594-B3BA-E41D8F381324.dcik
The original messages could be of the order of 3MB and the client's
network pipe wasn't so big: GZip was a saviour :)
Jon
David Rees wrote:
> On 3/15/06, David Kerber <dc...@verizon.net> wrote:
>> Are there any adjustments I can do to my Axis settings to reduce the
>> bandwidth usage on my SOAP requests?
>
> XML compresses very well, typically I have seen compression ratios over 10x!
>
> The key is to get your clients and servers configured to handle
> content compression. If you have Tomcat behind Apache, use
> mod_deflate. If Tomcat is running standalone, have a look at the
> default server.xml to turn it on.
>
> Finally, you have to pray that your clients have content compression support!
>
> The net result has been a huge bandwidth win in my experience, that
> when serving your typical html content.
>
> -Dave
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: How to reduce bandwidth (meaning message size) with Axis
Posted by David Rees <dr...@gmail.com>.
On 3/15/06, David Kerber <dc...@verizon.net> wrote:
> Are there any adjustments I can do to my Axis settings to reduce the
> bandwidth usage on my SOAP requests?
XML compresses very well, typically I have seen compression ratios over 10x!
The key is to get your clients and servers configured to handle
content compression. If you have Tomcat behind Apache, use
mod_deflate. If Tomcat is running standalone, have a look at the
default server.xml to turn it on.
Finally, you have to pray that your clients have content compression support!
The net result has been a huge bandwidth win in my experience, that
when serving your typical html content.
-Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
[OT] Re: How to reduce bandwidth (meaning message size) with Axis
Posted by Leon Rosenberg <ro...@googlemail.com>.
To answer your subject:
> How to reduce bandwidth (meaning message size) with Axis
don't use SOAP, use reliable, stable, high-performance protocols like CORBA :-)
Btw, never understood it, why should someone use SOAP?
regards
Leon
On 3/15/06, David Kerber <dc...@verizon.net> wrote:
> Are there any adjustments I can do to my Axis settings to reduce the
> bandwidth usage on my SOAP requests? In particular, I would like to
> know how I can get rid of the
...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: How to reduce bandwidth (meaning message size) with Axis
Posted by Mark Eggers <it...@yahoo.com>.
XML-RPC and SOAP serve two different areas, but you
might be able to cajole XML-RPC to accomplish what you
want.
. . . just some random thoughts while reading other
documentation.
/mde/
--- David Kerber <dc...@verizon.net> wrote:
> Are there any adjustments I can do to my Axis
> settings to reduce the
> bandwidth usage on my SOAP requests? In particular,
> I would like to
> know how I can get rid of the
>
"xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/""
> items in the
> argument elements. I'm using the minimum call
> settings, letting handle
> as much of it as possible automatically. If I need
> to set some
> parameters in code, that's fine, but please tell me
> which ones. My full
> SOAP request for a test run is below.
>
> The reason this is an issue is that this is an
> automated data collection
> system working over a WAN. Right now, we get about
> 800,000 data records
> per day, and are only about 20% deployed for one
> customer. BW is going
> to be a significant issue as we continue to roll
> this out.
>
> Thanks!
> Dave
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <soapenv:Envelope
>
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
>
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
>
> <soapenv:Body>
> <ns1:getDataLine
>
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
>
>
xmlns:ns1="http://localhost:8081/axis/EddService.jws">
> <ns1:arg0 xsi:type="soapenc:string"
>
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
> 1234501
> </ns1:arg0>
> <ns1:arg1 xsi:type="soapenc:string"
>
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
> 2/2/2
> </ns1:arg1>
> <ns1:arg2 xsi:type="soapenc:string"
>
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
> Wed Mar 15 16:44:57 EST 2006
> </ns1:arg2>
> <ns1:arg3 xsi:type="soapenc:string"
>
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
> This is the data line
> </ns1:arg3>
> </ns1:getDataLine>
> </soapenv:Body>
> </soapenv:Envelope>
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail:
> users-help@tomcat.apache.org
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org