- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Dec 2016 19:52:52 +0000
- To: public-secondscreen@w3.org
Okay, I am starting to understand what you are getting at. Thanks for your patience. The question is whether the availability promise/object is tied to the lifetime of the request that created them, which means they are created once and only once. Or, if they can be GCed independently from the request and recreated later. I believe the intention is that the developer can use the lifetime of the availability object to control when the browser is engaged in continuous monitoring of displays, and responsible usage would discard the object when the site isn't offering a UX to start presentation. We didn't add a specific `discard()` or `dispose()` API for this; that doesn't seem to be a common Web idiom. Unless we go that route, GC should be able to discard the availability object/promise independent of the request, and in that case, we would need to recreate them if getAvailability() is called again. @schien Does that make sense? Any other input? -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/388#issuecomment-264958260 using your GitHub account
Received on Monday, 5 December 2016 19:53:12 UTC