As I write this article, there is so much of excitement in the internet community about Microsoft's unveiling of the Hailstorm initiative with a vision for anytime, anywhere, user-centric based Web Services.
Everyday a huge number of business organizations are jumping onto the Web Services bandwagon to deliver software as a service by exposing their business processes as Web Services. They also collaborate and aggregate with other Web Services. This allows them to a complete a business process by leveraging existing infrastructure provided by other tested & proven web services that are specialized in their own business domains.
The power of XML and SOAP together with initiatives like WSDL (Web Services Description Language) make it easy for applications to connect to web services at communication endpoints that are deployed in other platforms, thus enabling disparate applications on different platforms to talk to each other and leverage each other's services seamlessly. Furthermore, standards like the UDDI (Universal Description, Discovery and Integration) allow businesses to discover web services that provide the kind of services and offerings they are looking for. The remoting framework that's provided with the .NET platform makes it easy to create and deploy web services. It provides the infrastructure you need such as various hosting options, message formatters, transport channels, lifetime management and activation policies. The .NET remoting building blocks that we saw in this article will help you create robust and scalable web services that meet the needs of your business process. Hopefully, this article will get you started in your journey in discovering the richness and robustness of this powerful architecture.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
/ 64 
