Compression is supported from the service only at this point in 2.5. There is a technote on the sforce site that was done in the 2.0 time frame that is usable for 2.5. Compression is accomplished by using http headers and .Net SoapAttributeExtensions. The sample has client to service as well as service to client compression, but as I stated above, 2.5 currently only supports service to client.
Let me know if you need clarification on the compression strategy.
I'm still a little confused. I've setup my application as shown in the example but it does not seem to be using the compression classes. Do you have any 2.5 samples specifically as to what should change in the web reference?
Compression is enable on our app servers via a configuration file. The mods where made to the config file to allow service to client compression several weeks ago. Unfortunately, that config file has a different release process than do code changes and did not get released. It should be in production by Friday morning.
Compression is supported by the web service, both inbound and outbound (from salesforce.com and to salesforce.com). Having said that, a bug was recently reported that manifests as a significant delay from the web service when sending a compressed SOAP message from the client. The patch for this bug is due out this week (probably near the end of the week).
The technote on the sforce site for implementing compression in Visual Studio is in the process of being updated so that the sample code properly reflects a recommended implementation. I am including the sample code here. Please check for the new technote next week in the resources section of sforce.com.
Hi Glenn,
Compression is supported from the service only at this point in 2.5. There is a technote on the sforce site that was done in the 2.0 time frame that is usable for 2.5. Compression is accomplished by using http headers and .Net SoapAttributeExtensions. The sample has client to service as well as service to client compression, but as I stated above, 2.5 currently only supports service to client.
Let me know if you need clarification on the compression strategy.
http://www.sforce.com/us/resources/tn-8.jsp
Dave;
I'm still a little confused. I've setup my application as shown in the example but it does not seem to be using the compression classes. Do you have any 2.5 samples specifically as to what should change in the web reference?
Regards;
GlennW
Hi GlennW,
On further review....
Compression is enable on our app servers via a configuration file. The mods where made to the config file to allow service to client compression several weeks ago. Unfortunately, that config file has a different release process than do code changes and did not get released. It should be in production by Friday morning.
My apologies.
Cheers
Please Let me know if Soap Compresssion is enabled, so i can use it for my apps
regards,
Gagan
Hi Gagan,
Compression is supported by the web service, both inbound and outbound (from salesforce.com and to salesforce.com). Having said that, a bug was recently reported that manifests as a significant delay from the web service when sending a compressed SOAP message from the client. The patch for this bug is due out this week (probably near the end of the week).
The technote on the sforce site for implementing compression in Visual Studio is in the process of being updated so that the sample code properly reflects a recommended implementation. I am including the sample code here. Please check for the new technote next week in the resources section of sforce.com.
Cheers.
I've just tried the sample, but I get an error in the ReadResponse, Xml Deserialize, invalid Xml. Anyone else seen this?
Thanks
Hi Darren,
Check out the new technote at http://www.sforce.com/resources/tn-8.jsp. This is updated and a better method of implementing compression.