Groups | Blog | Home
all groups > dotnet web services enhancements > september 2006 >

dotnet web services enhancements : Reducing overall packet size



clivec
9/13/2006 9:16:02 AM
I have a WSE3 application (desktop client and a server hosted as a service,
no IIS involved) that makes a lot of calls at times. The actual payload is
small so most of the network traffic is the XML of the envelope etc. Looking
around the web I can find help on compressing the payload part of the soap
message but none on reducing the size of the rest of the message. Looking at
the network traffic with a packet sniffer sometimes shows an entire TCP
packet of 1460 bytes that contains nothing but the SOAP stuff with may actual
data (sometimes as small as just the word "OK") being forced into another
packet entirely.

Is it possible to reduce the overhead of each soap call? Or should I be
Pablo Cibraro [MVP]
9/13/2006 1:45:45 PM
Hi,

Have you checked one of these solutions ?

1. Web Service Compression :
http://weblogs.asp.net/pglavich/archive/2004/01/24/62475.aspx
2. HTTP 1.1 Compression:
http://www.dotnetjunkies.com/Tutorial/90D3B3E0-6544-4594-B3BA-E41D8F381324.dcik

Both solutions compress the entire SOAP message. (They do not compress only
the payload)

Well, WCF offers a similar solution to compress the entire SOAP messages,
but the main advantage, it can work with any transport layer (HTTP, TCP,
etc).

Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax

[quoted text, click to view]

John Saunders
9/13/2006 3:22:19 PM
[quoted text, click to view]

It may be that your web service is too fine-grained. You may want more of a
Service Oriented Architecture than an RPC. That is, make each Web Service
Operation about providing one large service, rather than having the
operations each provide some small piece of functionality with an "OK"
response.

John

AddThis Social Bookmark Button