In Previous Blog we have discussed about the SOAP Encoding.Today we will discuss about the SOAP via HTTP in Android Training in Chandigarh
SOAP is not tied to any one transport protocol. In fact, SOAP can be transport via SMITP, FTP, IBM's MQSeries, or Microsoft Message Queuing (MSMO). However, the SOAP specification includes details on HTTP only, and HTTP remains the most popular SOAP Transport protocol.
Quite Logically, SOAP requests are sent via an HTTP Request and SOAP responses are returned within the content of the HTTP response. While SOAP requests can be sent via an HTTP response. While SOAP requests can be sent via an HTTP GET, the specification includes details on HTTP POST only. (HTTP POST is preferred because most servers place a character limit on GET requests). Additionally, both HTTP Requests and responses are required to set their content type to text/XML.
As an additional requirement, clients must specify a SOAP Action header. The SOAP ACTION header is a server-specific URI used to indicate the intent of the request. This makes it possible to quickly determine the nature of the SOAP request, without actually examining the SOAP message PAYLOAD. In practice, the header is frequently used by firewalls as a mechanism for blocking out SOAP requests or for quickly dispatching SOAP message to specific SOAP servers.
The SOAP specification mandates that the client must provide a SOAP Action header, but the actual value of the SOAP Action header is dependent on the SOAP server implementation. This SOAP via HTTP we will learn with Android Training in Chandigarh.
For Example : To Access the Alta Vista Babel Fish translation service,hosted by XMethods, one must specify the urn:xmethodsBabeIFish#BabelFish as the SOAPACTION header. Even if the server does not require a full SOAPAction header. Even if the server does not require a full SOAP Action header, the Client must specify an empty string(""), or null value.
SOAP is not tied to any one transport protocol. In fact, SOAP can be transport via SMITP, FTP, IBM's MQSeries, or Microsoft Message Queuing (MSMO). However, the SOAP specification includes details on HTTP only, and HTTP remains the most popular SOAP Transport protocol.
Quite Logically, SOAP requests are sent via an HTTP Request and SOAP responses are returned within the content of the HTTP response. While SOAP requests can be sent via an HTTP response. While SOAP requests can be sent via an HTTP GET, the specification includes details on HTTP POST only. (HTTP POST is preferred because most servers place a character limit on GET requests). Additionally, both HTTP Requests and responses are required to set their content type to text/XML.
As an additional requirement, clients must specify a SOAP Action header. The SOAP ACTION header is a server-specific URI used to indicate the intent of the request. This makes it possible to quickly determine the nature of the SOAP request, without actually examining the SOAP message PAYLOAD. In practice, the header is frequently used by firewalls as a mechanism for blocking out SOAP requests or for quickly dispatching SOAP message to specific SOAP servers.
The SOAP specification mandates that the client must provide a SOAP Action header, but the actual value of the SOAP Action header is dependent on the SOAP server implementation. This SOAP via HTTP we will learn with Android Training in Chandigarh.
For Example : To Access the Alta Vista Babel Fish translation service,hosted by XMethods, one must specify the urn:xmethodsBabeIFish#BabelFish as the SOAPACTION header. Even if the server does not require a full SOAPAction header. Even if the server does not require a full SOAP Action header, the Client must specify an empty string(""), or null value.
0 comments:
Post a Comment
Note: only a member of this blog may post a comment.