- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Feb 2016 15:26:46 +0000
- To: public-secondscreen@w3.org
@mfoltzgoogle wrote: > A wants to receive these final messages from B. Despite what I thought initially, at the API level in both WebRTC and WebSockets, A *cannot* receive these final messages even if it wants to (state is switched to `closing` immediately when `close()` is called and the specs require user agents to discard any message when state is not `connected`). This makes sense, receiving a message after calling `close()` seems counter-intuitive. So, for me, the main use case for closing seems to be for debugging. In the WebSocket case, this gives the web app a way to detect that the WebSocket server is misbehaving or taking an unusual amount of time... but that could well be done by the user agent itself without exposing this transient state (e.g. through warnings in the console). I'm not convinced this warrants the introduction of a `closing` state. -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/240#issuecomment-178633251 using your GitHub account
Received on Tuesday, 2 February 2016 15:26:48 UTC