DCS Policies
DCS enables you to configure client-side caching, and the way in which messages are encoded, by implementing the following two built-in policies:
- Caching Policy. You can specify this policy at the operation level for selected operations in a service. It enables caching of client requests and server responses, to avoid latency in systems where distributed services and limited bandwidth are possible factors affecting responsiveness. The caching policy is configurable, and it enables you to specify properties such as the expiration time of the cache. Cached responses are stored in a local SQL Server 3.5 Compact Edition database on the client computer. The proxy that the client uses to communicate with the service examines the local cache for a response that matches the client request, and if it finds one, it returns the cached response to the client and does not communicate with the service instance. Caching can also improve the availability of a service. If a service instance becomes temporarily unavailable.
- TCP/IP Policy. Services hosted in IIS version 7 with Windows Activation Service (WAS) can leverage the TCP/IP binding policy. TCP/IP requires less Network traffic than SOAP. However
- Compression Policy. CCF quick starts provides sample of compression policy. The compression policy allows to compress/uncompress the messages with GZip