Protocol 

Purpose

The main idea of adding client protocols is to implement additional features (functionalities) in replaceable units, which can be independent of the runtime core or enhance the runtime functionality. They are not really SOAP modules, since underlying message format may not be SOAP at all and they may not require the message at all. So if you regard client protocols as entities that provide some features, it is easy to understand why the base interface for all ClientProtocol-s and ClientTransportBinding-s is called FeatureProvider interface.

This section contains detaild information about:

·        FeatureProvider Interface

·        PropertyContext Interface

·        AbstractProtocol Interface

·        HTTPTransport Interface

·        Protocol Implementation Details