Event synchronization method, system, client and server

Abstract

The invention discloses an event synchronization method, an event synchronization system, a client and a server. The embodiment of the invention comprises the following steps of: transmitting a latest data acquisition request; receiving an event identifier from the server by socket connection with the server; and matching a monitor for monitoring an event of the event identifier according to the received event identifier, calling a callback function corresponding to the event, and executing a synchronization operation indicated by the callback function. The embodiment of the invention can timely return corresponding data to the client, improves the efficiency of the client and the server because the client is not required to set a timer to periodically repeatedly transmit requests to the server, and avoids user experiences with unfinished long connection loading and influence on the displaying of a browser of the client.

Description

technical field [0001] The present invention relates to the field of computer technology, in particular to an event synchronization method, system, client and server. Background technique [0002] The client and the server communicate through HTTP (hypertext transfer protocol, hypertext transfer protocol). In actual application, the client needs to obtain the data of the server in real time. For example, the alarm presentation of the management object in the network management software, the user needs to observe the alarm on the user interface within the shortest time after the alarm occurs, and repair the alarm fault in time. [0003] At present, there are two existing technical solutions for obtaining the latest data of the server in real time and realizing synchronization of events between the client and the server. The first existing technology is: the client sets a timer in the page; the client sends a request to obtain the latest data of the service at regular interva...

AI Technical Summary

Problems solved by technology

[0004] During the practice and research of the prior art, the inventors of the present invention found that the prior art obtains the latest data of the server by periodically sending a request, and if the data of the server does not change, it also keeps updating according to the timer Sending requests, these invalid requests will consume the performance and resources of the client and server. In addition, periodic sending of requests cannot meet the needs of some modules with high real-time performance. Due to multiple functions, your module needs to send real-time requests. A timer performs periodic refresh operations, occupying client resources and affecting the execution efficiency of the entire client.

The HTTP long connection of the prior art 2 occupies the number of connections of the server and affects other normal interface requests. The HTTP long connection cannot be implemented under the connection timeout mechanism in the current mainstream server; in different client browsers, the long connection state The processing is inconsistent. The progress bar at the lower end of browsers such as IE will show that the loading is not completed, and the user experience is not good. In addition, the HTTP1.1 specification stipulates that the client cannot establish more than two HTTP connections with the server, otherwise the new connection will be blocked. , with limited use

Images