The difference between a TCP long connection and a short connection

1. TCP Connections

When the TCP protocol is used in network communication, before a true read-write operation, a connection must be established between the server and the client, and when the read and write operation is complete, they can release the connection when they no longer need the connection, and the connection is established with a handshake of three times, and the release takes 4 shakes. So each connection is built to require resource consumption and time consumption.

Classic three-time handshake schematic:

Classic four-time handshake close diagram:

2. TCP Short Connection

We simulate the TCP short connection, the client initiates a connection request to the server, the server receives the request, and the two sides establish the connection. The client sends a message to the server, the server responds to the client, and then a read and write is done, and either of the two sides can initiate a close operation, although it is generally the client that initiates the next action. Why, the general server will not reply to the client immediately after the shutdown of the connection, of course, do not exclude special circumstances. From the above description, short connections typically only pass a read-write operation between Client/server

The advantage of a short connection is that it is simpler to manage, the connections that exist are useful connections, and no additional control is required.

3.TCP Long Connection

Next we simulate the long connection, the client initiates a connection to the server, the server accepts the client connection, and the two sides establish the connection. Once the client and server have completed a read and write, the connection between them is not actively closed, and subsequent read and write operations continue to use the connection.

First of all, the TCP/IP explained in detail on the TCP live function, the main function for the server application, server applications want to know whether the customer host crashes, so that customers can use resources on behalf of. If the customer has disappeared, leaving a half-open connection on the server, and the server is waiting for data from the client, the server should be far from waiting for the client's data, which is trying to detect the Half-open connection on the server side.

If a given connection does not have any action within two hours, the server sends a probe message segment to the client, and the client host must be in one of the following 4 states: The client host is still running and can be reached from the server. The client's TCP response is normal, and the server is aware that the other is normal, the server in two hours after the live timer reset. The client host has crashed and is shutting down or restarting. In either case, the client's TCP is not responding. The server will not be able to receive a response to the probe and timeout after 75 seconds. A total of 10 such probes are sent by the server, each interval of 75 seconds. If the server does not receive a response, it believes that the client host has shut down and terminated the connection. The client host crashed and has restarted. The server will receive a response to its live probe, which is a reset that causes the server to terminate the connection. The client is running normally, but the server is unreachable, and this is similar to 2, where TCP can find no response from the probe.

As you can see from the above, the main function of TCP protection is to detect the survival of long connection, but there is a problem, the survival function of the detection cycle is too long, there is it is only to detect the survival of TCP connections, belong to a more refined approach, encounter malicious connection, the function is not enough to keep alive.

In a long connected application scenario, the client side generally does not actively shut down their connection, if the connection between client and server, if not shut down, there will be a problem, as the client connection is more and more, the server sooner or later can not carry the time, At this point, the server side needs to take some policies, such as closing some long time no read and write events occur, so that some malicious connections can prevent the server side of the service damage, if the conditions can be allowed to the client machine for granularity, limit the maximum number of long connections per client, This can completely avoid the pain of some of the client's backend service.

Long connection and short connection is the result of the client and server to take the shutdown strategy, specific application scenarios using specific strategies, there is no perfect choice, only the right choice.

Reference:

1. TCP/IP Detailed volume a

Turn from: http://www.cnblogs.com/beifei/archive/2011/06/26/2090611.html

Origin: http://www.cnblogs.com/liuyong/

Alibaba Cloud Hot Products
Elastic Compute Service (ECS)	Dedicated Host (DDH)	ApsaraDB RDS for MySQL (RDS)	ApsaraDB for PolarDB(PolarDB)	AnalyticDB for PostgreSQL (ADB for PG)
AnalyticDB for MySQL(ADB for MySQL)	Data Transmission Service (DTS)	Server Load Balancer (SLB)	Global Accelerator (GA)	Cloud Enterprise Network (CEN)
Object Storage Service (OSS)	Content Delivery Network (CDN)	Short Message Service (SMS)	Container Service for Kubernetes (ACK)	Data Lake Analytics (DLA)
ApsaraDB for Redis (Redis)	ApsaraDB for MongoDB (MongoDB)	NAT Gateway	VPN Gateway	Cloud Firewall
Anti-DDoS	Web Application Firewall (WAF)	Log Service	DataWorks	MaxCompute
Elastic MapReduce (EMR)	Elasticsearch