Communication software don't work at work (or background), heartbeat mechanism can be used to determine the state of the client, but in the process of communication? Software in use process, the client must be connection state, then the heartbeat mechanism still work? That is to say, the heartbeat packets are always be sent? Or just don't work in the software to be sent?

CodePudding user response:

There is no answer?

CodePudding user response:

What's the good of tangled,

Protocol is defined, with a timer, timer hair go, as long as the processing, can quickly passed for bai

Out of work or, set a timer, 2 seconds, data transceiver, start the heartbeat packets sent bai

Are very easy to implement

CodePudding user response:

The heartbeat is to create their software to send packages

CodePudding user response:

From the purpose in a data communication really don't need a heartbeat packets, but actual implementation in a simple, generally do not distinguish between, heartbeat packets or timing

CodePudding user response:

Heartbeat mechanism is mainly in order to avoid the intermediate routing initiative to close the connection when no data transmission, this phenomenon in the early days of mobile applications in comparison, do you want to heart, should track their application scenarios to determine