search
HomeJavajavaTutorialThe principles and basic knowledge of WebSocket to implement Java background message push

1. What is WebSocket

The WebSocket protocol is a new network protocol based on TCP. It implements full-duplex communication between the browser and the server - allowing the server to proactively send information to the client.

2. Implementation Principle

In the process of implementing websocket connection, a websocket connection request needs to be sent through the browser, and then the server sends a response. This process is usually called "handshake". In the WebSocket API, the browser and the server only need to perform a handshake action, and then a fast channel is formed between the browser and the server. Data can be transmitted directly between the two.

3. Advantages

In the previous message push mechanism, Ajax polling was used, and the browser automatically issued a request at a specific time interval. The server's messages are actively pulled back. This method consumes a lot of resources because it is essentially an HTTP request and is very clumsy. WebSocket completes a handshake between the browser and the server. After the connection is established, the server can actively transmit data to the client, and the client can also send data to the server at any time.

4.The difference between WebSocket and Socket

 1.WebSocket:

    1. ##The establishment phase of websocket communication relies on the http protocol. The initial handshake phase is the http protocol. After the handshake is completed, it switches to the websocket protocol and is completely separated from the http protocol.

    2. When establishing communication, the client actively initiates a connection request and the server passively listens.

    3. Once the communication connection is established, the communication is in "full-duplex" mode. In other words, both the server and the client can send data freely at any time, which is very suitable for business scenarios where the server wants to actively push real-time data.

    4. The interaction mode is no longer the "request-response" mode, and the communication protocol is completely designed by the developer.


    5. The communication data is based on "frame", which can transmit text data or binary data directly, with high efficiency. Of course, developers also have to consider technical details such as packaging, unpacking, and numbering.

    6.  2.Socket:
    7. The server monitors communication and passively provides services; the client actively initiates a connection request to the server, Communication is established.

    8. Every interaction is: the client actively initiates a request (request), and the server passively responds (response).

    9. The server cannot actively push data to the client.

    10. #The communication data is based on text format. Binary data (such as pictures, etc.) must be converted into text using base64 and other means before it can be transmitted.


5.WebSocket client:

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

twenty one

twenty two

twenty three

twenty four

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

var websocket = null;

var host = document.location.host;

var username = "${loginUsername}"; // Get the userName of the currently logged in person

// alert(username)

//Determine whether the current browser supports WebSocket

if ('WebSocket' in window) {

alert("The browser supports Websocket")

websocket = new WebSocket('ws://' host '/mm-dorado/webSocket/' username);

} else {

alert('Current browser Not support websocket')

}

//Callback method for connection errors

websocket.onerror = function() {

 alert("WebSocket connection error")

setMessageInnerHTML("WebSocket connection error");

};

//Callback method for successful connection establishment

websocket.onopen = function() {

 alert("WebSocket connection successful")

setMessageInnerHTML("WebSocket connection successful");

}

//Callback method for receiving message

websocket.onmessage = function(event) {

alert("Callback method of receiving message")

alert("This is the message pushed in the background:" event.data);

websocket.close();

  alert("webSocket has been closed!")

}

//Callback method for connection closing

websocket.onclose = function() {

setMessageInnerHTML("WebSocket connection closed");

}

//Listen to the window closing event. When the window is closed, actively close the websocket connection to prevent the window from closing before the connection is disconnected. The server will throw an exception.

window.onbeforeunload = function() {

closeWebSocket();

}

//Close WebSocket connection

function closeWebSocket() {

websocket.close();

}

//Display the message on the web page

function setMessageInnerHTML(innerHTML) {

       document.getElementById('message').innerHTML = innerHTML '<br>' ;

}

6. WebSocket server (java background):

1. Core class:

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

twenty one

twenty two

twenty three

twenty four

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90

91

92

93

package com.mes.util;

import java.io.IOException;

import java.util.Map;

import java.util.concurrent.ConcurrentHashMap;

import javax.websocket.OnClose;

import javax.websocket.OnError;

import javax.websocket.OnMessage;

import javax.websocket.OnOpen;

import javax.websocket.Session;

import javax.websocket.server.PathParam;

import javax.websocket.server.ServerEndpoint;

import org.springframework.stereotype.Component;

import org.springframework.stereotype.Service;

import com.google.gson.JsonObject;

import net.sf.json.JSONObject;

@ServerEndpoint("/webSocket/{username}")

public class WebSocket {

       private static int onlineCount = 0;

       private static Map<string websocket> clients = </string>new ConcurrentHashMap<string websocket>(); </string>

        private Session session;

        private String username;

<p><code>                                                                    

       

@OnOpen

     

public void onOpen(@PathParam(" username") String username, Session session) throws IOException {

       

 

            

this.username = username;

          

this.session = session;

                                                                  

         

addOnlineCount();

<p><code>            clients.put(username, this);

<p><code>            System.out.println("已连接");

        

       

        @OnClose 

        public void onClose() throws IOException { 

<p><code>            clients.remove(username); 

<p><code>            subOnlineCount(); 

        

       

        @OnMessage 

        public void onMessage(String message) throws IOException { 

       

<p><code>            JSONObject jsonTo = JSONObject.fromObject(message); 

<p><code>            String mes = (String) jsonTo.get("message");

<p><code>             

<p><code>            if (!jsonTo.get("To").equals("All")){ 

<p><code>                sendMessageTo(mes, jsonTo.get("To").toString()); 

<p><code>            }else

<p><code>                sendMessageAll("给所有人"); 

<p><code>            

        

       

        @OnError 

        public void onError(Session session, Throwable error) { 

<p><code>            error.printStackTrace(); 

        

       

        public void sendMessageTo(String message, String To) throws IOException { 

<p><code>            // session.getBasicRemote().sendText(message); 

<p><code>            //session.getAsyncRemote().sendText(message); 

<p><code>            for (WebSocket item : clients.values()) { 

<p><code>                if (item.username.equals(To) ) 

<p><code>                    item.session.getAsyncRemote().sendText(message); 

<p><code>            

        

           

        public void sendMessageAll(String message) throws IOException { 

<p><code>            for (WebSocket item : clients.values()) { 

<p><code>                item.session.getAsyncRemote().sendText(message); 

<p><code>            

        

       

        public static synchronized int getOnlineCount() { 

<p><code>            return onlineCount; 

        

       

        public static synchronized void addOnlineCount() { 

<p><code>            WebSocket.onlineCount ; 

        

       

        public static synchronized void subOnlineCount() { 

<p><code>            WebSocket.onlineCount--; 

        

       

        public static synchronized Map<string websocket> getClients() { </string>

<p><code>            return clients; 

        

}

  2.在自己代码中的调用:

1

2

3

4

5

WebSocket ws = new WebSocket();

JSONObject jo = new JSONObject();

jo.put("message""这是后台返回的消息!");

jo.put("To",invIO.getIoEmployeeUid());

ws.onMessage(jo.toString());

  7.所需maven依赖:

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

<!-- webSocket 开始-->

<dependency></dependency>

    <groupid>javax.websocket</groupid>

    <artifactid>javax.websocket-api</artifactid>

    <version></version>1.1

    <scope>provided</scope>

 

<dependency></dependency>

    <groupid>javax</groupid>

    <artifactid>javaee-api</artifactid>

    <version></version>7.0

    <scope>provided</scope>

<!-- webSocket 结束-->

相关文章:

Java中websocket消息推送

一个基于WebSocket的WEB消息推送框架

相关视频:

Websocket视频教程

The above is the detailed content of The principles and basic knowledge of WebSocket to implement Java background message push. For more information, please follow other related articles on the PHP Chinese website!

Statement
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Why is Java a popular choice for developing cross-platform desktop applications?Why is Java a popular choice for developing cross-platform desktop applications?Apr 25, 2025 am 12:23 AM

Javaispopularforcross-platformdesktopapplicationsduetoits"WriteOnce,RunAnywhere"philosophy.1)ItusesbytecodethatrunsonanyJVM-equippedplatform.2)LibrarieslikeSwingandJavaFXhelpcreatenative-lookingUIs.3)Itsextensivestandardlibrarysupportscompr

Discuss situations where writing platform-specific code in Java might be necessary.Discuss situations where writing platform-specific code in Java might be necessary.Apr 25, 2025 am 12:22 AM

Reasons for writing platform-specific code in Java include access to specific operating system features, interacting with specific hardware, and optimizing performance. 1) Use JNA or JNI to access the Windows registry; 2) Interact with Linux-specific hardware drivers through JNI; 3) Use Metal to optimize gaming performance on macOS through JNI. Nevertheless, writing platform-specific code can affect the portability of the code, increase complexity, and potentially pose performance overhead and security risks.

What are the future trends in Java development that relate to platform independence?What are the future trends in Java development that relate to platform independence?Apr 25, 2025 am 12:12 AM

Java will further enhance platform independence through cloud-native applications, multi-platform deployment and cross-language interoperability. 1) Cloud native applications will use GraalVM and Quarkus to increase startup speed. 2) Java will be extended to embedded devices, mobile devices and quantum computers. 3) Through GraalVM, Java will seamlessly integrate with languages ​​such as Python and JavaScript to enhance cross-language interoperability.

How does the strong typing of Java contribute to platform independence?How does the strong typing of Java contribute to platform independence?Apr 25, 2025 am 12:11 AM

Java's strong typed system ensures platform independence through type safety, unified type conversion and polymorphism. 1) Type safety performs type checking at compile time to avoid runtime errors; 2) Unified type conversion rules are consistent across all platforms; 3) Polymorphism and interface mechanisms make the code behave consistently on different platforms.

Explain how Java Native Interface (JNI) can compromise platform independence.Explain how Java Native Interface (JNI) can compromise platform independence.Apr 25, 2025 am 12:07 AM

JNI will destroy Java's platform independence. 1) JNI requires local libraries for a specific platform, 2) local code needs to be compiled and linked on the target platform, 3) Different versions of the operating system or JVM may require different local library versions, 4) local code may introduce security vulnerabilities or cause program crashes.

Are there any emerging technologies that threaten or enhance Java's platform independence?Are there any emerging technologies that threaten or enhance Java's platform independence?Apr 24, 2025 am 12:11 AM

Emerging technologies pose both threats and enhancements to Java's platform independence. 1) Cloud computing and containerization technologies such as Docker enhance Java's platform independence, but need to be optimized to adapt to different cloud environments. 2) WebAssembly compiles Java code through GraalVM, extending its platform independence, but it needs to compete with other languages ​​for performance.

What are the different implementations of the JVM, and do they all provide the same level of platform independence?What are the different implementations of the JVM, and do they all provide the same level of platform independence?Apr 24, 2025 am 12:10 AM

Different JVM implementations can provide platform independence, but their performance is slightly different. 1. OracleHotSpot and OpenJDKJVM perform similarly in platform independence, but OpenJDK may require additional configuration. 2. IBMJ9JVM performs optimization on specific operating systems. 3. GraalVM supports multiple languages ​​and requires additional configuration. 4. AzulZingJVM requires specific platform adjustments.

How does platform independence reduce development costs and time?How does platform independence reduce development costs and time?Apr 24, 2025 am 12:08 AM

Platform independence reduces development costs and shortens development time by running the same set of code on multiple operating systems. Specifically, it is manifested as: 1. Reduce development time, only one set of code is required; 2. Reduce maintenance costs and unify the testing process; 3. Quick iteration and team collaboration to simplify the deployment process.

See all articles

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

PhpStorm Mac version

PhpStorm Mac version

The latest (2018.2.1) professional PHP integrated development tool

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Linux new version

SublimeText3 Linux new version

SublimeText3 Linux latest version

mPDF

mPDF

mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

SAP NetWeaver Server Adapter for Eclipse

SAP NetWeaver Server Adapter for Eclipse

Integrate Eclipse with SAP NetWeaver application server.