Flash through the Xmlsocket Monitoring production system (1)

xml| Monitoring

but b/s system structure is not omnipotent, due to its work mechanism limitations, in some areas, the previous use of B/s architecture is difficult to achieve the requirements of the function. Typically, Web pages and most Web applications use a working mechanism called request/response:

O users click on a hyperlink, or submit a form. The
O browser sends a request to the server. The
O Server initiates a session.
o The server sends the data to the browser after it has been processed.
o The server closes the session and the browser displays the data.

We can see that using the B/s architecture to design software, there is no way to avoid two limitations: passivity and hysteresis. First of all, the user must through the browser request, the server can respond, in some areas, such as timely monitoring, the need for the server in a specific case, the initiative to send data to the client, and the use of traditional B/s architecture technology, to achieve this goal is very difficult. Secondly, each request of the server must start a session, plus the time consumed by the service-side processing and network transmission, which naturally forms the lag of the client.

Perhaps some readers, will raise objections, chat room is using B/s architecture, why the server can every few seconds, the chat room to send the speeches of each person? In fact, chat room is still using B/s system structure of the request/response mechanism, only the client sends a request every few seconds, the curious reader can look at the source of the chat room webpage, can find such a statement in the head of the source code:
Its function is to send a request every 2 seconds.

When designing software, often to the industrial production system for timely monitoring, at any time to understand the operation of the production system, but in the past, if the adoption of the web is difficult to ensure timeliness, at the same time, every few seconds to send requests to the server, both waste network resources, but also bring additional burdens to the system. If you want to use B/s system structure, of course, there are methods, using applets, due to the limitations of Java security, must be a security configuration for each client, can this and C/s architecture and what is different, has lost the B/s system structure of "thin customer" advantages.

can be released from Flash 5, where the XML and Xmlsocket technology to solve the B/s system structure passivity and hysteresis restrictions, without the security restrictions of Java, the new Flash MX in this has been greatly enhanced. This article will introduce the use of XML and Xmlsocket technology to monitor the production system in time, at the same time, in order to test the convenience, introduced a simulation of the server program. (All of the descriptions in this article will be based on Falsh's latest version of Flash MX.) )

but b/s system structure is not omnipotent, due to its work mechanism limitations, in some areas, the previous use of B/s architecture is difficult to achieve the requirements of the function. Typically, Web pages and most Web applications use a working mechanism called request/response:

O users click on a hyperlink, or submit a form. The
O browser sends a request to the server. The
O Server initiates a session.
o The server sends the data to the browser after it has been processed.
o The server closes the session and the browser displays the data.

We can see that using the B/s architecture to design software, there is no way to avoid two limitations: passivity and hysteresis. First of all, the user must through the browser request, the server can respond, in some areas, such as timely monitoring, the need for the server in a specific case, the initiative to send data to the client, and the use of traditional B/s architecture technology, to achieve this goal is very difficult. Secondly, each request of the server must start a session, plus the time consumed by the service-side processing and network transmission, which naturally forms the lag of the client.

Perhaps some readers, will raise objections, chat room is using B/s architecture, why the server can every few seconds, the chat room to send the speeches of each person? In fact, chat room is still using B/s system structure of the request/response mechanism, only the client sends a request every few seconds, the curious reader can look at the source of the chat room webpage, can find such a statement in the head of the source code:
Its function is to send a request every 2 seconds.

When designing software, often to the industrial production system for timely monitoring, at any time to understand the operation of the production system, but in the past, if the adoption of the web is difficult to ensure timeliness, at the same time, every few seconds to send requests to the server, both waste network resources, but also bring additional burdens to the system. If you want to use B/s system structure, of course, there are methods, using applets, due to the limitations of Java security, must be a security configuration for each client, can this and C/s architecture and what is different, has lost the B/s system structure of "thin customer" advantages.

can be released from Flash 5, where the XML and Xmlsocket technology to solve the B/s system structure passivity and hysteresis restrictions, without the security restrictions of Java, the new Flash MX in this has been greatly enhanced. This article will introduce the use of XML and Xmlsocket technology to monitor the production system in time, at the same time, in order to test the convenience, introduced a simulation of the server program. (All of the descriptions in this article will be based on Falsh's latest version of Flash MX.) )