Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any planning about exposing heartbeat events or notification about disconnection? #23

Open
ghost opened this issue Nov 15, 2016 · 0 comments

Comments

@ghost
Copy link

ghost commented Nov 15, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants