-
Notifications
You must be signed in to change notification settings - Fork 63
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
Is there a way to check if connection is still alive? #8
Comments
Client-to-Server Pings may help you. |
thx, I'll try to implement a ping if there was no activity since ~5 minutes. |
Ping is a bit heavy on the server. Some servers (like ejabberd on SaaS) support whitespace ping. |
@mdosch Sorry it took so long, but I am finally working on the disconnect detection and adding some way to trigger reconnect. |
@mdosch I think the new ClientManager should do what you need. It reconnects automatically when the connection is lost. I guess we can close this ticket now. You can also monitor progress on connection loss detection that will add an active way to detect connection loss: #35 |
Thank you, I will check it out. :)
|
Although I am using the StreamManager as in your echo bot example, see here it seems to still not work properly. |
This is the output from one of my bots in journalctl:
|
First thank you for this library and the echo bot example. I was able to build a simple bot without programming experience following the example, although I have to admit at the start I used code from this repo.
But despite reading in the library a lot it is still not clear to me how I could check whether the connection is still alive. My bot works pretty well till it stops working due to a network flaw/reconnect. Could you please give me a hint at which modules/functions I should have a closer look?
The text was updated successfully, but these errors were encountered: