4. XML application classification
In general, XML applications can be divided into four categories:
(1) Apply when customers need to interact with different data sources. The data may come from different databases, and they all have different complex formats. But customers interact with these databases only in one standard language, that is XML. Due to the customization and scalability of XML, it is sufficient to express various types of data. After receiving the data, customers can process it or pass it between different databases. In short, in this type of application, XML solves the problem of unified interface of data. However, unlike other data delivery standards, XML does not define the specific specifications for the occurrence of data in the data file, but instead attaches tags to the data to express the logical structure and meaning of the data. This makes XML a specification that programs can automatically understand.
(2) It is applied to distribute a large amount of computing load on the client, that is, the client can select and create different applications according to their needs to process data, while the server only needs to issue the same XML file. The above example is still discussed. For example, according to the traditional "client/server" working method, the client sends different requests to the server and the server responds separately. This not only increases the load on the server itself, but also network managers must investigate various user needs in advance to make different programs. However, if the user's needs are complex and changeable, it is inappropriate to concentrate all business logic on the server side, because the programmers on the server side may not have time to meet the many application needs and keep up with the changes in demand, and both parties are very passive. The application of XML gives the initiative to process data to the customer. What the server does is to encapsulate the data into the XML file as perfectly and accurately as possible, and each one takes its own needs and performs its own duties. The self-interpretation of XML enables clients to understand the logical structure and meaning of the data while receiving it, thus making widespread and general distributed computing possible.
(3) Apply to present the same data to different users in different appearances. This application can also be reflected in the above example. It is similar to the same script, but we can express it in different forms such as TV series, movies, dramas, cartoons, etc. This application will pave the way for the personalized and stylized development of the network user interface.
(4) Apply to the network agent to edit, add or decrease the obtained information to meet the needs of individual users. Some customers obtain data not for direct use but for organizing their own databases as needed. For example, the Ministry of Education has established a huge question bank. During the exam, it takes out several questions in the question bank to form the test papers, and then encapsulates the test papers into an XML file. Next is the most exciting part. Each school allows it to pass a filter to filter out all the answers, and then send it to each candidate. Unfiltered content can be sent directly to the teacher. Of course, after the exam, you can also send another answer compilation. In addition, the XML file can also include other related information such as difficulty coefficients, error rates in previous years, etc. In this way, only a few mini programs can be used, and the same XML file can be converted into multiple files and transmitted to different users.
In general, XML applications can be divided into four categories:
(1) Apply when customers need to interact with different data sources. The data may come from different databases, and they all have different complex formats. But customers interact with these databases only in one standard language, that is XML. Due to the customization and scalability of XML, it is sufficient to express various types of data. After receiving the data, customers can process it or pass it between different databases. In short, in this type of application, XML solves the problem of unified interface of data. However, unlike other data delivery standards, XML does not define the specific specifications for the occurrence of data in the data file, but instead attaches tags to the data to express the logical structure and meaning of the data. This makes XML a specification that programs can automatically understand.
(2) It is applied to distribute a large amount of computing load on the client, that is, the client can select and create different applications according to their needs to process data, while the server only needs to issue the same XML file. The above example is still discussed. For example, according to the traditional "client/server" working method, the client sends different requests to the server and the server responds separately. This not only increases the load on the server itself, but also network managers must investigate various user needs in advance to make different programs. However, if the user's needs are complex and changeable, it is inappropriate to concentrate all business logic on the server side, because the programmers on the server side may not have time to meet the many application needs and keep up with the changes in demand, and both parties are very passive. The application of XML gives the initiative to process data to the customer. What the server does is to encapsulate the data into the XML file as perfectly and accurately as possible, and each one takes its own needs and performs its own duties. The self-interpretation of XML enables clients to understand the logical structure and meaning of the data while receiving it, thus making widespread and general distributed computing possible.
(3) Apply to present the same data to different users in different appearances. This application can also be reflected in the above example. It is similar to the same script, but we can express it in different forms such as TV series, movies, dramas, cartoons, etc. This application will pave the way for the personalized and stylized development of the network user interface.
(4) Apply to the network agent to edit, add or decrease the obtained information to meet the needs of individual users. Some customers obtain data not for direct use but for organizing their own databases as needed. For example, the Ministry of Education has established a huge question bank. During the exam, it takes out several questions in the question bank to form the test papers, and then encapsulates the test papers into an XML file. Next is the most exciting part. Each school allows it to pass a filter to filter out all the answers, and then send it to each candidate. Unfiltered content can be sent directly to the teacher. Of course, after the exam, you can also send another answer compilation. In addition, the XML file can also include other related information such as difficulty coefficients, error rates in previous years, etc. In this way, only a few mini programs can be used, and the same XML file can be converted into multiple files and transmitted to different users.