Shulou(Shulou.com)06/01 Report--

This article is about how to communicate between the browser and the server through WebSocket. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

Nowadays, there is a need to realize the communication between browser and server based on websocket. Since I had not used websocket before, I roughly searched the Internet for an integration solution for websocket. The solution found on the Internet is roughly as follows:

1. Based on spring implementation, add spring-websocket dependency, annotate, configure the corresponding interceptor and path

two。 The springBoot-based approach is essentially based on spring.

3. Based on J2EE application server, it seems that websocket support is provided from tomcat7, which can be implemented directly with @ WebsocketEnd. This annotation is provided by the servlet package.

They have a feature, that is, based on servlet implementation (the third way has not been verified).

However, for various reasons, I need to implement this process based on struts2, that is, based on Filter. Baidu has found a solution for a long time: use metacharacters in the interceptor of struts2 to open up a path, and then intercept it without success!

Finally, the websocket scheme is implemented by means of spring+ annotations.

For other reasons, it is necessary to transfer the scheme based on spirngmvc, that is, servelt, to struts, that is, Filer. Therefore, after some thinking and practice, we finally found the corresponding solution here to record it, in order to help colleagues to solve the corresponding needs:

First, use the stack trace to find the servlet websocket to execute the process:

The stack is as follows:

Then, combined with the execution process of springmvc, it is analyzed:

After analysis, we can move the entire model logic from servelt to the corresponding Filter, but in the face of many configurations, how to migrate smoothly is a problem. I deal with it like this. When you execute on the mvc side, hit a breakpoint, check the corresponding variable types in memory, and then construct manually:

The original code looks like this:

In practice, those numerous configurations and @ Configuration are used for the corresponding configuration with springmvc, as well as the initialization of local parameters here. So I can totally build one by hand.

The code I created is as follows:

Other logic is based directly on struts.

After practice, it is feasible and easy to use, and no other problems have been found yet.

Thank you for reading! This is the end of the article on "how to communicate between the browser and the server through WebSocket". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.