How to design a heartbeat package for asynchronous sockets

It can be controlled using a separate thread. Send a heartbeat packet (format defined by yourself), the timer starts, and if it is received within the timeout period, it will continue to send a new heartbeat packet, and if it does not receive a reply after the timeout, it will enter the error handling.

const int keepalivesize = 12;

static byte keepalive(int onoff, int keepalivetime, int keepaliveinterval)

byte buffer = new byte[keepalivesize];

return buffer;

Where to set up:

socket clientsocket = ;After endaccept.

keepalive(0, 30000, 5000), null);

I've been reading this stuff lately, so you can add me to communicate.

Either end (or both) is triggered by a timer to send a specific string of bits at regular intervals.

After listening to and responding to the format bitstring, the heartbeat interval counter is reset to zero.

A dedicated thread is used for monitoring, and a heartbeat packet is sent if there is a certain amount of time idle.

For asynchronous sockets, multiple connections can be monitored by a single thread.

It is a form of socket long connection, you can open multiple customer service terminals and communicate with the server side on my side, normal communication Acceptance and sending have been achieved No problem, now the customer service side will send me a heartbeat packet every 30 seconds to detect whether it is connected to the server or normal, so I don't want to go to the database to establish a table to store its heartbeat data There is too much data.

Use a thread to monitor, and if Chang Min is idle for a certain amount of time, he sends a heartbeat packet. For asynchronous sockets, multiple raid connections can be monitored by one thread.

Heartbeat is also a kind of data in data communication, and the special point is that it is sent at a timed time, so it is named after the shape of a heartbeat. Generally speaking, when a client connects to the server, it is necessary to ensure that the state of the connection is real, or to prevent some networks from automatically disconnecting when there is no data transmission for a long time.

Since you are using asynchronous socket communication, you should receive an exception in EndReceive.

Parse this exception and you're good to go.

I prefer to do it with synchronous socket communication + threads.

Of course, the same goes for asynchronous ones.