Easily Compress Traffic between Client and Server
Glenn Gailey commented
This is a big deal for Windows Phone-based OData apps as there is literally no workaround to enable gzip. Even the hacks that work for WCF clients in Silverlight can't be used with the OData client for Windows Phone, and phone customers are (for obvious reasons) very sensitive to network utilization.
Asbjørn Ulsberg commented
WCF creates the client-side proxy and if it doesn't include "Accept-Encoding: gzip", this is something that has to be enabled in WCF for the client-side proxy. For the server-side, enabling this in IIS will probably be sufficient.
HTTP protocol defines mechanism to negotiate compression between client and server. OData should leverage the existing industory standard.
sample headers of request:
sample header of response:
Dave Russell commented
I believe the currently generated client-side proxy sends requests that don't pass the "Supports GZIP / DEFLATE" headers - and that there is no exposed client-side hook that lets you override this behaviour - regardless of whether the transport supports it or not.
Kristofer Andersson commented
umm, the choice to use gzip is a transport level thing, configurable in IIS. No need to deal with that at the service level IMO...(?)