- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Feb 2015 09:22:32 +0000
- To: public-secondscreen@w3.org
I think the current events based approach [1] is a better fit for conveying the availability information in the Presentation API, since the data involved is not large. The relevant Promises Guide section is Recurring Events [2]. An example of an API that builds upon the Streams API is e.g. TCP and UDP Socket API [3]. This API potentially produces large amounts of data and as such is a good fit for Streams API. [1] http://w3c.github.io/presentation-api/#the-onavailablechange-eventhandler [2] http://www.w3.org/2001/tag/doc/promises-guide#recurring-events [3] http://www.w3.org/2012/sysapps/tcp-udp-sockets/ -- GitHub Notif of comment by anssiko See https://github.com/w3c/presentation-api/issues/11#issuecomment-73668064
Received on Tuesday, 10 February 2015 09:22:40 UTC