You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: