- From: Anton Vayvod via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 May 2015 13:47:34 +0000
- To: public-secondscreen@w3.org
MediaRouteProvider is not for the app that needs to get screen availability. There's MediaRouter.removeCallback() that means the app doesn't want to get updates about the routes anymore. It is advised to remove callback in onStop/onPause. The UA could definitely stop discovery for the pages that are not visible and resume it when the page becomes visible. I don't think the page should explicitly manage the power / CPU / bandwidth consumption by the UA's discovery process. I also don't think the UA should rely on the page to do the right thing in order to stop discovery. I also think that having to wait for two promises to be resolved to simply get availability status as in https://github.com/w3c/presentation-api/issues/81#issuecomment-101039366 is an overkill and is as non-standard as having an event fire immediately as soon as the event handler is attached (what we are trying to solve). -- GitHub Notif of comment by avayvod See https://github.com/w3c/presentation-api/issues/81#issuecomment-101668994
Received on Wednesday, 13 May 2015 13:47:35 UTC