Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...
.NET Forum / ASP.NET / Web Services / September 2006

Tip: Looking for answers? Try searching our database.

Reducing overall packet size

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
clivec - 13 Sep 2006 17:16 GMT
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
looking to WCF? My app has to work over LAN, WAN and internet.
Reply to this Message
Pablo Cibraro [MVP] - 13 Sep 2006 18:45 GMT
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

>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
[quoted text clipped - 11 lines]
> Is it possible to reduce the overhead of each soap call? Or should I be
> looking to WCF? My app has to work over LAN, WAN and internet.
Reply to this Message
John Saunders - 13 Sep 2006 20:22 GMT
>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
[quoted text clipped - 11 lines]
> Is it possible to reduce the overhead of each soap call? Or should I be
> looking to WCF? My app has to work over LAN, WAN and internet.

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
Reply to this Message

 Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage
Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.