SOAP stands for Simple Object Access Protocol. It is just a set of standards for doing remote procedure calls using XML. So if the client wants to execute a procedure on the server, the client builds a description of the call -- name of function and arguments -- into an XML message. The server takes the XML message, extracts the arguments, executes the function call, and returns the result to the client in another XML message. It is particularly useful in web services because if you use the web, you already have XML parsing and HTTP transport. The client doesn't need any new operating system support if you can do those two things. So any client that can connect to the internet (at least with a current version browser) can do web services with SOAP. A good tutorial (unless you hate Microsoft) is Aaron Skonnard SOAP: The Simple Object Access Protocol, Microsoft Internet Developer (January 2000)
SOAP comes into picture when a web site contacts some other site in the back ground to get som einformation? It specifies the standards on how you make the remote procedure calls. Vasu
What a wonderful world!
Joined: Apr 23, 2002
Originally posted by vasu maj: SOAP comes into picture when a web site contacts some other site in the back ground to get som einformation? It specifies the standards on how you make the remote procedure calls. Vasu
That's one way, but not the only way. You use SOAP when you want to perform some sort of function call on a remote system. A web site never really needs to be involved, except that the most common way to send a SOAP message is the same way a web page sends a message with a 'Submit' button. SOAP is a particular standard for describing a RPC call and for describing the returned result in XML. It does not have to happen in the back ground, and neither the client nor the server have to be a web site. The XML messages can even be sent and received using other technologies such as SMTP (Email) or JMS (Java Messaging Service).