W3C home > Mailing lists > Public > public-secondscreen@w3.org > April 2015

Re: [presentation-api] Rethinking availability monitoring

From: Oleg Beletski via GitHub <sysbot+gh@w3.org>
Date: Tue, 28 Apr 2015 07:25:09 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-96957202-1430205908-sysbot+gh@w3.org>
```AvailabilityListener``` definitely can get the job done for both 
modes. One issue still has to be sorted out. I understood from 
@avayvod post [1] about  ```AvailabilityListener``` that discovery 
process is running even if ```onavailablechanged``` callback is not 
set and ```available``` attribute can still change in runtime 
depending on the availability of the external screens. That means that
 monitoring has to be explicitly stopped to make  mode 1 example 
complete.  Would it make scene to add ```cancel``` method to the  
```AvailabilityListener```? Any better ideas?
```
listenForAvailability.then(function(listener) {
  if (listener.available) {
  /* Stop the listener here */
  offerPresentation();
  }
}
```

[1] 
https://lists.w3.org/Archives/Public/public-secondscreen/2015Apr/0079.html


-- 
GitHub Notif of comment by obeletski
See 
https://github.com/w3c/presentation-api/issues/81#issuecomment-96957202
Received on Tuesday, 28 April 2015 07:25:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 28 April 2015 07:25:11 UTC