No answer from server HEARBEAT ACK
wadx opened this issue · 6 comments
wadx commented
Client seems sending HEARTBEATs right way, but server never answers, and after some time disconnect client.
UndarkAido commented
Oh, is that what's happening? Hrm. Maybe they changed how to send heartbeats? Busy right now, but I'll try to look into it when I have a chance. I may not need to switch to Beast. I still want to at some point though, I could use just Beast instead of Websocket++ & CurlPP.
Cleroth commented
Does thaht mean this bot is currently unusable?
UndarkAido commented
Yes, it does. I'm currently refactoring it, but stuff had been hectic.
…On Fri, Jun 16, 2017, 1:31 AM Cleroth ***@***.***> wrote:
Does thaht mean this is currently unusable?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHE_YkF9I_w96dawDSyU-qMXgZ6Xsri7ks5sEiFZgaJpZM4MaM9v>
.
Cleroth commented
Understandable, but may want to update the README with a warning or something...
NotUnlikeTheWaves commented
Unless I'm mistaken, #9 fixed this
UndarkAido commented
Yup looking like it.