When an XML Web service client uses the HTTP-POST protocol, by default parameters are encoded within the HTTP body using URL encoding rules and uses plain XML for the response. This protocol uses classes that derive from System.Web.Services.Protocols.MimeFormatter to encode parameters and return values into standard MIME formats. The encoders to use are specified in the service description.

If you are building an XML Web service client using ASP.NET, then a proxy class deriving indirectly or directly from System.Web.Services.Protocols.WebClientProtocol needs to be created for the XML Web service you want to call. When the XML Web service client is calling using HTTP, derive the proxy class System.Web.Services.Protocols.HttpSimpleClientProtocol, which in turn derives from System.Web.Services.Protocols.WebClientProtocol.

System.Web.Services.Protocols.HttpGetClientProtocol and System.Web.Services.Protocols.HttpPostClientProtocol derive from System.Web.Services.Protocols.HttpSimpleClientProtocol, providing the support for calling an XML Web service method using HTTP-GET and HTTP-POST respectively. Clients calling an XML Web service using SOAP should derive from System.Web.Services.Protocols.SoapHttpClientProtocol.

For details on building a proxy class, see [<topic://cpconcreatingwebserviceproxy>].

Namespace: System.Web.Services.Protocols
Assembly: System.Web.Services (in System.Web.Services.dll)
Assembly Versions: 1.0.5000.0, 2.0.0.0