| Windows Communication Foundation (WCF) | |
|---|---|
| Original author | Microsoft |
| Developer | .NET Foundation |
| Initial release | November 21, 2006; 19 years ago (2006-11-21) |
| Stable release | v3.4.0 / August 18, 2022; 3 years ago (2022-08-18) |
| Repository | github |
| Written in | C# |
| Operating system | Linux,macOS,Windows |
| Platform | .NET Framework,.NET |
| Predecessor | Web Services Enhancements |
| Type | Software framework |
| License | MIT License |
| Website | docs |
TheWindows Communication Foundation (WCF), previously known asIndigo, is afree and open-sourceruntime and a set ofAPIs in the.NET Framework for building connected,service-oriented applications.[1][2]
.NET Core 1.0, released 2016, did not support WCF server side code. WCF support was added to the platform with support for .NET Core 3.1, .NET 5, and .NET 6 in 2022.[3]
WCF is a tool often used to implement and deploy aservice-oriented architecture (SOA).It is designed using service-oriented architecture principles to supportdistributed computing whereservices have remoteconsumers. Clients can consume multiple services; services can be consumed by multiple clients. Services areloosely coupled to each other. Services typically have aWSDLinterface (Web Services Description Language) that any WCF client can use to consume the service, regardless of which platform the service is hosted on. WCF implements many advanced Web services (WS) standards such asWS-Addressing,WS-ReliableMessaging andWS-Security. With the release of.NET Framework 4.0, WCF also providesRSS Syndication Services,WS-Discovery, routing and better support forREST services.
A WCF client connects to a WCF service via anendpoint. Each service exposes its contract via one or more endpoints. An endpoint has an address (which is a URL specifying where the endpoint can be accessed) and binding properties that specify how the data will be transferred.
Themnemonic "ABC" can be used to rememberaddress/binding/contract. Binding specifies whatcommunication protocols are used to access the service, whether security mechanisms are to be used, and the like. WCF includes predefined bindings for most common communication protocols such asSOAP over HTTP, SOAP over TCP, and SOAP over Message Queues, etc. Interaction between WCF endpoint and client is done using a SOAP envelope. SOAP envelopes are in simple XML form, which makes WCF platform-independent. When a client wants to access the service via an endpoint, it not only needs to know the contract, but it also has to adhere to the binding specified by the endpoint. Thus, both client and server must have compatible endpoints.
With the release of the .NET Framework 3.5 in November 2007, Microsoft released an encoder that added support for theJSONserialization format to WCF.[4]
Behaviors are types that modify or extend service or client functionality. Behaviors allow the developer to create custom processing, transformation, or inspection that is applied to messages as they are sent or received. Some examples of uses for behaviors are:
Behaviors implement theIServiceBehavior interface for service extensions, theIEndpointBehavior for endpoints, theIContractBehavior interface for service contracts, or theIOperationBehavior for operations. Service behaviors are used for message processing across a service, rather than processing that would be specific to a single operation.
WCF supports interoperability with WCF applications running on the same Windows machine or WCF running on a different Windows machines or standard Web services built on platforms such asJava running on Windows or other operating systems. In addition to SOAP, WCF 4 supports non-SOAP XML,RSS,JSON, and binary formats for external communication via HTTP orHTTPS.[6]
| Overview | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Software |
| ||||||||||||
| Licenses | |||||||||||||
| Forges | |||||||||||||
| Related | |||||||||||||
