-
Notifications
You must be signed in to change notification settings - Fork 75
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
WebSocket - full-stream being disconnected at regular interval #59
Comments
Complementary information, the Python client using WS from https://github.com/CaliDog/certstream-python/blob/master/certstream/core.py#L20 works as expected. I suppose it's the heartbeat. |
Hi @adulau sorry for the delay in getting back to you.
Yep, Erlang's cowboy webserver (which certstream uses) will disconnect clients that are idle after I think it's 60s. Basically it can't tell if a client is idle or if something else has gone wrong since we don't have a message acknowledgement system (which would be quite some overhead performance wise). The simple solution is to send some data to the server at a specific interval, and the server will basically just ignore it, though it will stop your disconnect issue. Unfortunately I think our support for heartbeats is a bit scattered at the moment, I went to scope out what it'd take for golang for example and it seemed like a non-trivial effort. That said, I'm curious what language you're talking to certstream from, and if it'd make sense to make your language a supported one as well. Cheers! |
Ah here we go, check out |
A small question, the WS connection to the full-stream disconnects with code 1000 (successful close) at regular interval. I used various WS libraries and I have the same behaviour. I looked into web.ex but cannot find code triggering the close.
I use the latest 26dff90 and used the following Elixir version
Is it a common behaviour or a bug?
The text was updated successfully, but these errors were encountered: