Introduction to Extensibility
The Windows Communication Foundation (WCF) application model is designed to solve the greater part of the communication requirements of any distributed application. But there are always scenarios that the default application model and system-provided implementations do not support. The WCF extensibility model is intended to support custom scenarios by enabling you to modify system behavior at every level, even to the point of replacing the entire application model. This topic outlines the various areas of extension and points to more information about each.
You can extend:
The application runtime. This extends the dispatching and the processing of messages for the application. This area also includes extending the security system, the metadata system, the serialization system, and the bindings and binding elements that connect the application with the underlying channel system.
The channel and channel runtime. This extends the system that functions at the message level, providing protocol, transport, and encoding support.
The host runtime. This extends the relationship of the hosting application domain to the channel and application runtime.
Extending the Application Runtime
In WCF applications, there is a distinction between messages that are destined for a corresponding channel and messages that are destined for the application itself. Channel messages support some channel-related functionality, such as establishing a secure conversation or establishing a reliable session. These messages are not available to the application runtime; they are processed before the application layer is involved.
Application messages contain data that is destined for a client or service operation that you or your customer has created. These messages are available to the application-level extension system in message or object form, depending upon your needs.
All messages pass through the channel system; only application messages are passed from the channel system into the application. To create new channel-level functionality, you must extend the channel system. To create new application-level functionality, you must extend the service or client runtime (dispatchers and channel factories, respectively). For more information about extending the application runtime, see Extending ServiceHost and the Service Model Layer.
To build custom security mechanisms such as tokens and credentials, you must extend the security system. For more information, see Extending Security.
To expose your metadata in differently than the default, you must extend the metadata system. For more information, see Extending the Metadata System.
To build custom encoders, provide data surrogates, or other work involving the customization of transferred data, you must extend the serialization system. For more information, see Extending Encoders and Serializers.
To associate transport or protocol channels with the application layer, you must extend the binding system. For more information, see Extending Bindings.
Extending the Channel System
To create channels that support custom transports or protocol functionality, see Extending the Channel Layer.
Extending the Service Hosting System
To modify the relationship between the hosting application domain and the service host, you must extend the System.ServiceModel.Activation.ServiceHostFactory class. For more information, see Extending Hosting Using ServiceHostFactory.