Microsoft’s Dino Chiesa recently appeared on SearchSOA.com to discuss WCF, where it is at, how it got there. He said that WCF is pegged as a generalized approach to services-oriented development. Developers of distributed systems told MS they wanted fewer programming interfaces for communications, Chiesa writes.
They asked for a single generalized communications stack. Windows Communication Foundation (WCF) is the generalized programming framework for communications for Windows-based applications.
Excerpt: Using the extensibility in WCF, for example, people have built a service host for WCF services that detects changes in a policy repository, and if and when the policy for those services changes, the host stops and re-starts services with the new policy information. As another example, by default a WCF service will expose a modular WSDL, with XSD factored out into external documents. But some tools and Web services runtimes don’t deal well with this, and work better with a “flattened” WSDL. A custom service host in WCF can dynamically flatten the WSDL that is generated for a service, to support those tools. Other examples of extensibility: Endpoint behaviors in WCF can be used to implement the injection of custom behaviors into the endpoints of WCF services, and custom serialization logic, for example, to use a binary serialization format can be applied to any operation with an operation behavior. The extensibility of WCF enables all this flexibility.
Read Chiesa on Web services stacks - Windows Communication Foundation (WCF) - SearchSOA.com