- From: Mark Foltz (Google) via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Oct 2020 18:50:49 +0000
- To: public-secondscreen@w3.org
I believe in the past we concluded that applications that wanted a signal about the liveness of the connection should implement their own keep-alive and not assume that the user agent would do so on their behalf. Some reasons why I think that's the right approach: 1. Applications may want to be more/less aggressive on this. 2. Implementing a universal keep-alive in the user agent increases network traffic and hurts battery life. 3. Some protocols (like QUIC, used in OSP, or cloud-based connections) are not connection-oriented and "operational" may not have a clear-cut definition. 4. The user agent may want to close idle connections and reconnect in the background. -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/485#issuecomment-709524360 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 15 October 2020 18:50:51 UTC