xml web services allow applications to share data.
xml web services can be called across platforms and operating systems and regardless of programming language.
.net is microsoft's platform for xml web services.
the xml revolution although deceptively simple, xml is turning the way we build and use software inside out. the web revolutionized how users talk to applications. xml is revolutionizing how applications talk to other applications--or more broadly, how computers talk to other computers--by providing a universal data format that lets data be easily adapted or transformed. xml-based standards, which include soap and uddi, comprise the open methodology for application-to-application communication known as xml web services. xml web services: a universal language xml web services allow applications to communicate regardless of operating system or programming language via the internet. they can be implemented on any platform and are defined through public standards organizations such as the w3c. and with xml web services, not only can applications share data, but they can also invoke capabilities from other applications without regard to how other applications were built. sharing data through xml allows them to be independent of each other while simultaneously giving them the ability to loosely link themselves into a collaborating group that performs a particular task. web sites vs. xml web services web sites are about presenting information to a user: they are the communication vehicle for servers to talk to users. xml web services, on the other hand, offer a direct means for applications to interact with other applications. applications hosted internally, as well as on remote systems, can communicate via the internet by using xml and soap messages. how xml web services connect applications here's a simple example: say you have an inventory system. if you don't connect it to anything else, it's not very valuable. you can track inventory, but it's a lot of work, and what that one system can do all by itself is limited. every item you sell needs to be entered not only into your inventory system, but also separately into your accounting system, and your customer account records. then you need to remember to order more of that item from your suppliers next time you place an order. the cost/benefit ratio is largely unappealing, because the gains from the system are close to the overhead costs of using it. however, if you connect your inventory system to your accounting system with xml, it gets more interesting. now, whenever you buy or sell something, the implications for your inventory and your cash flow can be tracked in one step. if you go further, and connect your warehouse management system, customer ordering system, supplier ordering systems, and your shipping company with xml, suddenly that inventory management system is worth a lot: you can do end-to-end management of your business while dealing with each transaction only once, instead of once for every system it affects. a lot less work, and a lot less room for errors. these connections can be made easily using xml web services. xml web services allow the applications to share information via the internet, regardless of the operating system or back-end software that the application is using. .net is about xml web services microsoft's xml web services platform is .net. the first set of xml web services microsoft is building is codenamed "hailstorm".
the xml revolution
