- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Jan 2016 18:01:17 +0000
- To: public-secondscreen@w3.org
I disagree. I think the closed event should signal exactly that: the messaging channel is closed, i.e. no more messages can be accepted through the channel. Pending requests to `send` may continue to be delivered but this would be best effort and at the discretion of the implementation. For example, if the channel has abruptly closed (because the destination context went away, or the underlying transport was disconnected) no further delivery would be possible, and I think writing a spec to enumerate all the potential cases when messages could or could not be delivered would be complex. I suggest the way forward is to land this PR and continue work in #240 on specifying a closing handshake, if it's an important use case to deliver messages to a closing/closed connection. -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/presentation-api/pull/239#issuecomment-172934911 using your GitHub account
Received on Tuesday, 19 January 2016 18:01:20 UTC