[presentation-api] Possibility for UA to close the connection when it is no longer operational (#485)

tidoust has just created a new issue for https://github.com/w3c/presentation-api:

== Possibility for UA to close the connection when it is no longer operational ==
Looking at the spec, the circumstances that may make a UA close a presentation connection are:
- [start a presentation connection](https://w3c.github.io/presentation-api/#dfn-start-a-presentation-connection) fails
- [establishing a presentation connection](https://w3c.github.io/presentation-api/#dfn-establish-a-presentation-connection) fails
- [close](https://w3c.github.io/presentation-api/#dom-presentationconnection-close) is called on either side
- [sending](https://w3c.github.io/presentation-api/#dfn-send-algorithm) or [receiving](https://w3c.github.io/presentation-api/#dfn-receive-algorithm) a message fails
- The [`PresentationConnection` object is discarded](https://w3c.github.io/presentation-api/#ref-for-dfn-start-closing-the-presentation-connection-2)

However, a user agent could also detect that the presentation connection is no longer operational on its own, e.g. because the other UA no longer responds to keep-alive requests. Should the spec mention that possibility too and allow the UA to signal that to the application? For instance, something like "The user agent may close the presentation connection with wentaway as closeReason when it detects that the connection is no longer operational" (and when it no longer feels that it can do something about it).

Memory may fail me, the group may have discussed that in the past :)


Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/485 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 10:19:24 UTC