You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have to know when did we lose connection to the peer endpoint in one of my projects.
For example, we pulled out the ethernet cable and expected our code to realize that the connection was somewhat broken.
In the log messages outputted by socket.io-poco, I can notice that several heartbeat request did not get corresponding heartbeat response in this situation. How ever, there is no API to expose the heartbeat events, just logging.
If there existed some API to expose heartbeat events, we can interprete the events and do some reconnection-trying logic at higher level.
Or we can make socket.io-poco to handle the reconnection logic automatically. As far as I know, this logic is not in socket.io-poco yet.
Or, am I totally misunderstanding this subject?
What is your opinion?
I am going to implement the heartbeat event exposing feature is you are busy. Because I need it in my project.
The text was updated successfully, but these errors were encountered:
I have to know when did we lose connection to the peer endpoint in one of my projects.
For example, we pulled out the ethernet cable and expected our code to realize that the connection was somewhat broken.
In the log messages outputted by socket.io-poco, I can notice that several heartbeat request did not get corresponding heartbeat response in this situation. How ever, there is no API to expose the heartbeat events, just logging.
If there existed some API to expose heartbeat events, we can interprete the events and do some reconnection-trying logic at higher level.
Or we can make socket.io-poco to handle the reconnection logic automatically. As far as I know, this logic is not in socket.io-poco yet.
Or, am I totally misunderstanding this subject?
What is your opinion?
I am going to implement the heartbeat event exposing feature is you are busy. Because I need it in my project.
The text was updated successfully, but these errors were encountered: