- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Nov 2016 08:27:28 +0000
- To: public-secondscreen@w3.org
About re-using the networking task source or not, internal discussions suggest the answer is "it depends". I raised an issue against the TAG's Design Principles spec last week: https://github.com/w3ctag/design-principles/issues/38 Initial feedback from @annevk suggests using a dedicated task source. That matches my understanding. I don't think the task source used by the Presentation API is going to affect the behavior that developers might expect to see. It does not make any sense to mix calls to the Presentation API and to Web Sockets and expect a Presentation API event to fire before/after an event fired by Web Sockets. As such, I would rather suggest to let implementers decide where they queue Presentation API tasks and create a "presentation task source" for the Presentation API. -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/360#issuecomment-263506616 using your GitHub account
Received on Tuesday, 29 November 2016 08:27:34 UTC