tag:blogger.com,1999:blog-8246382.post110841243676007599..comments2007-02-19T10:49:07.766-05:00bl0gg32http://www.blogger.com/profile/17700012969702551321noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-8246382.post-1108413417834081312005-02-14T15:36:57.836-05:002005-02-14T15:36:57.836-05:00Well, did not take that long ...<br /><br />Does not worth the trouble...<br /><br />One would ask: Not even for the %80 size reduction ? YES AND YES...<br /><br />Do this:<br />Enable compression on IIS6.0 (A challange by itself)<br />Enable HTTP GET on your web service. <br />Create the HEAVY-WEIGHT SOAP client proxy, that will help you to get all the types in the web service.<br />Create a web request (HTTP GET) to the web service.<br />Add a compression-enabling header to your request.<br />Get the response.<br />Check the response for compression.<br />If compressed, use ICSharpCode.SharpZipLib.dll to decompress it.<br /><br />You get the XML of the dataset...<br /><br />When you compress the XML and the text file, the difference in size is neglectible. In my case it was a 10 milliseconds difference on the WAN.bl0gg32http://www.blogger.com/profile/17700012969702551321noreply@blogger.com