- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 Jan 2016 19:42:15 +0000
- To: public-secondscreen@w3.org
Okay, another attempt uploaded. - It sets the connection state to `closed` immediately when `close()` is invoked, so the code from example 3 should be addressed. - It makes the "close a connection" task run at most once per connection, the first thing that causes the connection to close "wins" and gets to set the reason and message, later procedures are aborted. This would be simplified by adding a `closing` state to the connection which could be checked explicitly to prevent multiple close tasks from executing. However this state would be used primarily to support the specification and it's not clear if it needs to be exposed to the API client. Maybe add a side note that this internal state would be helpful to implementation? -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/presentation-api/pull/239#issuecomment-171756116 using your GitHub account
Received on Thursday, 14 January 2016 19:42:18 UTC