Re: Sending compressed XML over the internet?

Hi Olaf,

Thanks for the details.

In the client side im using mssoap.soapclient30 and on the server an IIS
virtual folder is configured to work with SOAP toolkit.

Yes compression on the soap client and web server sounds good. But I
couldn't find any useful tips on these.
Can you please advice on any of the resources?
Remote Proxy too is a good idea. I will check this. If you have any
resources on this please advice also.


Best regards,
Nadee



"Olaf.Doschke" <b2xhZi5kb3NjaGtlQHNldG1pY3MuZGU@xxxxxxxxxxxxx> wrote in
message news:OLeW#Qz1GHA.1288@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

ideally compression/decompression would not be done by the
client application and web service, but by the soap client and
the web server on which the web service resides.

Both of them would have to be configured to accept and do
transfer encoding. You would have to change nil in your app
or the web service, compression and decompression would be
done on the whole SOAP messages transparently.

So what do you use on the client and the server side?

client: "mssoap.soapclient30"? Westwinds wwSoap?
something else?

server: iis? setup of web service through soap toolkit?

If you have influence on both sides you may be able to
establish this kind of automatic transfer en/decoding.

This is quite normal for browser/web server. And as SOAP
is using http as the transfer protocol this should work
there too. I would have to figure out the details too.

Even if we don't manage that, how about setting up
a local and remote proxy?

Instead of the client connecting to the webservice directly
the local proxy first get's all soap messages, compresses
them, sends them to the remote proxy, who decompresses,
then forwards to the webservice and then returns the
response the other way around. This way the uncompressed
messages will only travel from client to local proxy and from
remote proxy to web server/service. Transfer in the internet/
intranet would be compressed.

Also not done as easy as said, but should be possible.

Bye, Olaf.




.

Relevant Pages

  • Re: SOAP Webservice C# / Axis2
    ... I'm trying to code a simple C# SOAP client wich query an Axis2 Java SOAP ... Server side code has been generated from a WSDL file. ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Soap Server in perl
    ... responce from the server. ... Sorry Ian I donot mean to say like that but actually I am new to perl ... and Perl in which you can install SOAP::Lite then you'll have to implement the SOAP support some other way. ... Move your module unchanged to your web server and write a generic SOAP dispatcher (designated by the proxy in the client) that hands off ...
    (comp.lang.perl.misc)
  • Re: Starting with SOAP
    ... But would your part be the SOAP ... client or the SOAP server? ... I built a form for a client, ... script on another server, ...
    (comp.lang.perl.misc)
  • Re: Starting with SOAP
    ... It has been suggested that SOAP would work for this. ... update some database that the script accesses? ... or the SOAP server? ... I built a form for a client, who now wants to take that data and pass it to another server so it can be used to update a page there. ...
    (comp.lang.perl.misc)
  • Re: Compression when browser does not support
    ... header to indicate to the server the ability ... Server behavior is in the form of allow/disallow compression IF the client ... negotiation (i.e. browser do not know server requires authentication before ...
    (microsoft.public.inetserver.iis)
Loading