1. The client creates an instance of the XML Web service proxy class on the same computer on |
which the client resides. |
2. The client calls a method on the proxy object. |
3. The XML Web services infrastructure on the client system serializes the method call and the |
arguments to the method into a SOAP request message and sends it to the XML Web service over the network. |
4. The infrastructure on the server on which the XML Web service resides deserializes the SOAP |
message and creates an instance of the XML Web service. The infrastructure then calls the actual web service method passing in the arguments on the XML Web service. |
5. The XML Web service executes the method and returns the value with any output parameters to |
the infrastructure. |
6. The infrastructure serializes the return value and the output parameters into a SOAP response |
message and sends them back to the client over the network. |
7. The infrastructure on the client computer deserializes the SOAP response containing the return |
value and the output parameters and sends them to the proxy object. |
The proxy object sends the return value and the output parameters to the client. |
As you can see from the preceding steps, the XML Web Services infrastructure provided by the .NET Framework plays an important role in building, deploying, and consuming Web services. In addition, Visual Studio 2005 provides tools that allow you to easily and effectively build, deploy, and publish your XML Web services using ASP.NET. |