Five different scenarios for using XML

Xml

1. Data exchange Using XML to Exchange data between applications and companies is no secret and should be ranked first. So why is XML so important in this field? The reason is that XML uses elements and attributes to describe the data. Throughout the data transfer process, XML retains data structures such as parent/child relationships. Several applications can share and parse the same XML file without having to use the traditional string parsing or dismantling process. 　　 Instead, the normal file does not describe each data segment (except in the header file), nor does it preserve the data relationship structure. Using XML for data Exchange can make your application more resilient, because you can access XML data using locations (like regular files) or with element names (from databases). 　　 2, Web Services Web Services is one of the most exciting revolutions that allows people with different systems and different programming languages to communicate and share data with each other. This is based on the fact that the Web server uses XML to exchange data between systems. The Exchange data is usually XML tagged, enabling the protocol to achieve the same specification, such as on the Simple Object Processing protocol (easy Objects Access Protocol, SOAP) platform. 　　 Soap can pass messages between objects that are constructed in different programming languages. This means that a C # object can communicate with a Java object. This communication can even occur between objects running on different operating systems. DCOM, CORBA, or Java RMI can only pass messages between tightly coupled objects, and soap can pass messages between loosely coupled objects. 　　 3. Content Management XML describes data only with elements and attributes, and does not provide a way to display data. In this way, XML provides an excellent way to mark content that is independent of platform and language. 　　 Using languages like XSLT makes it easy to convert XML files into various format files, such as HTML, WML, PDF, flat file, EDI, and so on. XML has the ability to run between different system platforms and transform into different format object files, making it a good choice in Content management application system. 　　 4. Web Integration More and more devices are now supporting XML as well. Allows Web developers to use XML to pass data between personal electronics assistants and browsers. 　　 Why would you send XML text directly into such a device? The purpose of this is to allow users to more of their own data display methods, more can experience the joy of practice. Regular client/service (c/s) in order to get the data to sort or replace the display format, the request must be sent to the server, while XML can process the data directly, without having to request a query to the server-return the results of the two-way "journey", while the device does not need to configure the database 　　 You can even modify the XML file on the device and return the results to the server. Imagine how much the impact of a refrigerator with Internet capabilities and XML-enabled refrigerators would bring to the market. You don't have to get up early to fetch milk! 　　 5, preparation Many applications store the configuration data in a variety of files, such as. INI file. Although such a file format has been in use for years and has always worked well, XML still makes it a better way to configure data for application tagging. Use. NET, such as XmlDocument and XmlTextReader, mark the configuration data as XML format, make it more readable, and easily integrate into the application system. An application that uses XML to make a file can easily process the data you need, without recompiling like any other application to modify and maintain the application system. 　　 As mentioned earlier, the five ways to use XML mentioned here do not cover all the scenarios. I hope these can help you think about how