CN104394212A - A method for real-time website push message - Google Patents

Abstract

The invention relates to the technical field of software development, in particular to a method for pushing messages by a real-time website. The invention sends a request to a server through a web client, and the server blocks the request and returns the request until data transmission or overtime occurs; after the JavaScript response processing function of the client side processes the information returned by the server, the request is sent again, and the connection is reestablished; when the client processes the received data and reestablishes the connection, the server may have new data arriving; the information is stored by the server side until the web client side reestablishes the connection; the client retrieves all information of the current server once; therefore, the website user can receive the message sent by the server in real time, and the message receiving delay is avoided. The invention relates to real-time communication between a server and a client.

Description

A method for real-time website push message

technical field

The invention relates to the technical field of software development, in particular to a method for pushing messages on a real-time website.

Background technique

Now is the era of information technology, which enables human beings to obtain and deliver all the achievements of civilization created by human beings in a faster and more convenient way. The lag of information will bring some unnecessary troubles and even major economic losses. The timeliness of information is particularly important, and respond to the information obtained in the first time. .

Contents of the invention

The technical problem to be solved by the present invention is to provide a method for pushing messages on a real-time website, so as to provide users with a timely and efficient method for obtaining information.

The technical scheme that the present invention solves the problems of the technologies described above is:

The request is sent to the server through the web client, and the server blocks the request until there is data transmission or timeout before returning; after the client JavaScript response processing function finishes processing the information returned by the server, it sends the request again and re-establishes the connection; when the client When processing the received data and re-establishing the connection, new data may arrive on the server side; this information will be saved by the server until the web client re-establishes the connection; the client will retrieve all the current server-side information at one time; thus website users The message sent by the server can be received in real time to avoid lagging in message reception.

Described method comprises the steps:

Step 1. First, the Bayeux protocol used by the client and server for interaction;

Step 2, the client initiates a handshake request to the server (on the /meta/handshake channel);

Step 3: The server receives the handshake request, and BayeuxServer creates an instance of a half-server object; after the server finishes processing the handshake request, it sends a response to the client;

Step 4. The client receives the response from the server to process the handshake request. If successful, then:

a. Initiate a subscription service request to the server;

b. Start the heartbeat mechanism with the server to exchange connection information;

Step 5: Initialize two service channels when the server restarts

a./service/privatechat custom channel

b./service/joinlisten custom channel

Step 6: The client initiates a subscription/service/privatechat service to the server, which is used to implement chat between users;

Step 7, start the heartbeat mechanism;

Step 8, heartbeat mechanism, establish HTTP long polling;

Step 9, the heartbeat mechanism allows the client to detect whether the server is closed, and allows the server to detect whether the client is closed;

Step 10, the connection message between the client and the server is always there, until either party decides to interrupt and send a disconnect message;

Step 11, the client can send a request to the server/service/joinlisten channel;

Step 12, all initialization work has been prepared, and information can be sent between clients arbitrarily.

The beneficial effect of the present invention is: through the method of real-time website pushing messages, users can obtain useful information in time, monitor the access status of web applications, realize timely discovery of problems and timely processing of problems, and greatly reduce the time that customers cannot access applications. Minimize losses.

Description of drawings

The present invention is further described below in conjunction with accompanying drawing:

Fig. 1 is a business flow chart of the present invention.

Detailed ways

As shown in the attached figure, the present invention sends a request to the server through the web client, and the server will block the request until there is data transmission or timeout before returning, and then the client JavaScript response processing function will process the information returned by the server, and then return to the server again. A request is made to re-establish the connection. When the client processes the received data and re-establishes the connection, new data may arrive on the server; this information will be saved by the server until the web client re-establishes the connection, and the client will retrieve all the current server-side information at one time , so that website users can receive the messages sent by the server in real time, avoiding delays in receiving messages and causing losses!

Let's take an application that pushes messages as an example to describe the implementation of this method:

Step 1. First, the Bayeux protocol used by the client and server for interaction;

Step 2: The client initiates a handshake request to the server (on the /meta/handshake channel). The Bayeux protocol requires that the first message sent by a new client is a handshake message;

Step 3, the server receives the handshake request, and BayeuxServer creates an instance of a half-server object (a ServerSession). After the server finishes processing the handshake request, it sends a response to the client;

Step 4. The client receives the response from the server to process the handshake request. If it is successful, the next thing to do is two things:

a. Initiate a request to the server to subscribe to the service.

b. Start the heartbeat mechanism with the server to exchange connection information;

Step 5. Two service channels are initialized when the server restarts

a./service/privatechat custom channel

b./service/joinlisten custom channel

Step 6: The client initiates a subscription/service/privatechat service to the server, which is used to implement chat between users

Step 7, start the heartbeat mechanism

Step 8, heartbeat mechanism, establish HTTP long polling.

Step 9, the heartbeat mechanism allows the client to detect whether the server is closed, and allows the server to detect whether the client is closed.

Step 10, the connection message between the client and the server has always been there, until either party decides to interrupt and send a disconnect message (send /meta/disconnect disconnect channel message)

Step 11, the client can send a request to the server /service/joinlisten channel

Step 12, all initialization work has been prepared, and information can be sent between clients arbitrarily.

Claims (2)

1. a method for real-time website PUSH message, is characterized in that: transmit a request to service end by web client, and server end blocking request is until have data transmission or time-out just to return; The process of client JavaScript response afterwards function, after processing the information that server returns, again sends request, re-establishes connection; When the data that client process receives, re-establish connection time, server end may have new data to arrive; These information can be preserved until web client re-establishes connection by serviced device end; Client is once by information retrieval all for current server end; Thus website user can the message that sends to service end of real-time reception, avoids message sink delayed.

2. the method for real-time website PUSH message according to claim 1, is characterized in that: described method comprises the steps:

The Bayeux agreement that 1st step, first client and service end adopt alternately;

2nd step, client initiate handshake request to service end (on/meta/handshake channel);

3rd step, service end receive handshake request, and BayeuxServer creates the example of one and half server objects; After service end processes handshake request, send response to client;

4th step, client receive the response of service end process handshake request, if success, then:

A. the request of subscription service is initiated to service end;

B. start the heartbeat mechanism with service end, exchange the information of connection;

Initialization two service channels when 5th step, service end are restarted

The self-defined channel of a./service/privatechat

The self-defined channel of b./service/joinlisten

6th step, client are initiated to service end subscriptions/service/privatechat and are served, and this service is used for the chat realized between user;

7th step, beginning heartbeat mechanism;

8th step, heartbeat mechanism, set up the long poll of HTTP;

Whether whether the 9th step, heartbeat mechanism, allow client to detect server and close, and allow service end detection client to close;

The message of the connection between the 10th step, client and server has always, until either party determines to interrupt and sends the message of a disconnect;

11st step, client can send request to service end/service/joinlisten channel;

12nd step, all initial work are all ready, just can send information arbitrarily between client.