W3C home > Mailing lists > Public > public-secondscreen@w3.org > September 2016

Re: [presentation-api] define the behavior for consecutive |getAvailability|

From: Mark Foltz via GitHub <sysbot+gh@w3.org>
Date: Fri, 30 Sep 2016 21:07:47 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-250852533-1475269665-sysbot+gh@w3.org>
Section 6.4 will need a bit of cleanup to make it consistent with 
reasonable behavior.  Here is what I am thinking.
- Annotate `getAvailability()` with `SameObject`.
- Define a *presentation availability* internal object for use in the 
algorithms.  There is exactly one of these for a given list of URLs 
regardless of the script context.
- Define a *presentation availability promise* which is created at 
most once per *presentation availability*.
- Make sure that only one PresentationAvailability is created per 
script context per *presentation availability*.  (This is an 
optimization, may not be strictly required.)
- Update conditions when an entry can be removed from the *set of 
availability objects*.

Can start after the PR for Issue #342 lands (which tweaks some text in
 this same section).

 


-- 
GitHub Notification of comment by mfoltzgoogle
Please view or discuss this issue at 
https://github.com/w3c/presentation-api/issues/335#issuecomment-250852533
 using your GitHub account
Received on Friday, 30 September 2016 21:07:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:19:01 UTC