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

Connection drop #2

Open
alferbus opened this issue Oct 5, 2018 · 0 comments
Open

Connection drop #2

alferbus opened this issue Oct 5, 2018 · 0 comments

Comments

@alferbus
Copy link

alferbus commented Oct 5, 2018

Hi! That's some cool repo you got here.
I've been recently doing some digging around with libcurl and I happened to find your software. When connection is lost or dropped, the event stream just freezes and there's no way to get it back up running unless I restart the client. Libcurl apparently does not yield any error code when connection is lost, and
just assumes you are in charge of keeping it alive.

"A libcurl-using application running in a known physical environment (e.g. an embedded device with only a single network connection) may want to act immediately if its lone network connection goes down. That can be achieved by having the application monitor the network connection on its own using an OS-specific mechanism, then signalling libcurl to abort (see also item 5.13)" https://curl.haxx.se/docs/faq.html#Why_doesn_t_curl_return_an_error

There must be some way to fix this. I was also wondering whether it's a server-related thing (see https://hpbn.co/server-sent-events-sse/ , server retry interval) but the test server I'm currently using (a private one) does not seem to do retries of any kind.

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

1 participant