Server message pushing method and device

Abstract

The invention discloses a server message pushing method and device. The message pushing method includes that a Websocket connection request of a client side is received, and the Websocket connection with the client side is established at a server side based on the Webscoket connection request; the server side transmits page messages based on the Websocket connection; and the Websocket connection established at the server side is integrated with a message-oriented middleware. The Websocket connection is unifiedly managed and distributed at the client side, and the Websocket connection is integrated with the message-oriented middleware, so that the message pushing efficiency of the server side is improved and the users' experience feeling is improved.

Description

technical field [0001] The present invention relates to the field of computers, in particular to a server message pushing method and device. Background technique [0002] In enterprise-level systems, especially in the development of cloud computing systems that need to realize continuous synchronization of server background data to client monitoring and instant event messages, under the BS architecture, how can the background data be pushed to the front end in an efficient, instant and stable manner? The page has always been a problem, especially the ability to support offline fetching of information. Two issues need to be considered here, one is the acquisition of news sources, and the other is the efficient and instant push of news. [0003] In the development of server push technology in the past, the most common way is to use ajax short polling and long polling. They all obtain data intermittently based on the original http request server, which belongs to server pull i...

AI Technical Summary

Problems solved by technology

Unable to decouple the offline environment

Obviously, server-level storage will have such disadvantages, so browser client-level storage must be considered. The most commonly used solution is to use browser cookies, but the cookie method also has the following two problems: data size: As a storage container, the size of the cookie is limited to about 4KB, which cannot meet the current complex business logic requirements and large-capacity information storage; network burden: the cookie will be attached to each HTTP request, in the header of HttpRequest and HttpResponse They are all to be transmitted, which is meaningless for the offline storage of messages and adds a lot of network burden

[0007] For the above-mentioned problems in related technologies, no effective solution has been proposed yet

Images