[presentation-api] Would a "closing" connection state be of any use?

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

== Would a "closing" connection state be of any use? ==
Both WebSockets and WebRTC data channels switch to a `closing` state 
when the closing procedure is started. The state switches to `closed` 
at the end of the closing handshake, in other words when the 
underlying protocol triggers some signal that the connection should be
 regarded as closed.

The `closing` state makes sense from a procedural perspective (this 
matches how the user agent is going to handle the closing process). I 
do not know why this state is exposed to Web apps, though. It seems to
 me that all use cases I can think of would equally work with only the
 `closed` state that we have in the Presentation API.

However, the rationale that led to the `closing` state in WebSockets 
and WebRTC data channels probably applies to `PresentationConnection` 
as well. So, question is: does anyone know that rationale?

Please view or discuss this issue at 
https://github.com/w3c/presentation-api/issues/240 using your GitHub 
account

Received on Tuesday, 12 January 2016 17:09:31 UTC