 |
| Total Answers and Comments: 4 |
Last Update: April 07, 2009 Asked by: Eman |
|
| | |
|
Submitted by: scorpioviper
SOAP is a XML based 'message' that a web service client can send to an actual web service (& vice versa). The reason why this message is termed as a 'protocol' is because the XML semantics inside this message is based on a well know standard understood by both the actual web service & all its clients.
Having said this, note that this XML based 'message' does not have any capability on its own whatsoever to physically travel from the so-called web service client (which may be on your desktop PC) to the actual web service (which may be on the server). Because after all, this messages is nothing but a set of XML tags sitting conceptually in a virtual world.
And this is where an underlying 'network technology' is required to physically take this XML based 'message' from the web service client to the actual web service. This underlying network technology can be anything eg: HTTP, raw TCP sockets, SMTP, JMS etc. Note that this network technology is also referred to as a 'protocol'.
So dont get confused between the 'message' which is a 'Communication Protocol' between a web service & its clients, & the actual network technology used to physically move it across the network which is actually referred to as a 'Transport Protocol'.
Shortest possible & technically correct answer to the question
---------------------------------------------------------------------------------
A web service & its clients communicate with each other using SOAP protocol as the 'Communication Protocol' whereas the underlying 'Transport Protocol' can be anything depending on its implementation; right from HTTP, TCP, Raw Sockets, JMS, SMTP etc.
Above answer was rated as good by the following members:
goksn, bino75 |
Go To Top
|
0 
1