An existing project, our system USES the.net B/S structure, front end of the public, the user to click through page control hardware, hardware is provided by third party hardware vendors, they provide a method of communication TCP

I imagine, in a WEB service background to establish and maintain a long TCP server link to communicate with a third party (front end request quantity is very big, if repeated handshake will reduce the efficiency and response speed), and end user page, ajax request WEB server program, the server to communicate with a third party, and returns the result after processing, return to the page

Question: how to implement the backend applications, technologies and solutions with

CodePudding user response:

Now I'm doing a similar project, I use webservices, on the server and communication equipment, the data received via TCP way sent to the web page, page do receive monitoring, which has a better suggestion

CodePudding user response:

This scenario should be simple socket, ajax requests to the web interface, find a socket in the interface and communication equipment, concrete can resist, or suggest forecast pressure test again,

CodePudding user response:

Websocket perfect solution to your problem,

CodePudding user response:

What is the theoretical basis of the idea you plan?
HTTP is a stateless protocol, and client round after the session is out of the WEB server applications, how can you maintain the TCP long links?
# 3 right, websocket to solve your problem

CodePudding user response:

Originally don't want to do a service program, using a single thread, use the singleton handle the client request,

CodePudding user response:

Finally how to solve the building Lord, I now have a similar application scenario

CodePudding user response:

SignalR the building Lord considered