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
This project already supports reconnecting with a retry timer when the connection closes (#7/#26). Additionally, we should consider a connection to be dead if we did not receive any data for a timeout period (default could be 600s?). The server is expected to send regular heartbeat/ping messages (such as the empty comment :\n) to keep the connection alive if there is no activity (each 15-60s seems reasonable). This is particularly useful in the event where the socket connection may die silently such as due to power outages or network failure.
This project already supports reconnecting with a retry timer when the connection closes (#7/#26). Additionally, we should consider a connection to be dead if we did not receive any data for a timeout period (default could be 600s?). The server is expected to send regular heartbeat/ping messages (such as the empty comment
:\n
) to keep the connection alive if there is no activity (each 15-60s seems reasonable). This is particularly useful in the event where the socket connection may die silently such as due to power outages or network failure.Refs clue/reactphp-redis#132, https://github.com/reactphp/http#timeouts, https://launchdarkly.github.io/dotnet-eventsource/api/LaunchDarkly.EventSource.ReadTimeoutException.html
We welcome contributions, reach out if you want to support this project or become a sponsor ❤️
The text was updated successfully, but these errors were encountered: