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

Re: [presentation-api] Rethinking availability monitoring

From: mwatson2 via GitHub <sysbot+gh@w3.org>
Date: Thu, 14 May 2015 00:46:23 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-101866750-1431564383-sysbot+gh@w3.org>
On Mon, May 11, 2015 at 2:08 AM, Anssi Kostiainen 
<notifications@github.com>
wrote:

> We seem to be in agreement that [1] with some tweaks [2] is a better
> solution than what we currently have in the spec.
>
> @avayvod <https://github.com/avayvod> Could you update your proposal
> baking in feedback by F2F?
>
> @obeletski <https://github.com/obeletski> Is this a functional gap 
or a
> quality of implementation issue (performance, power/resource 
consumption
> etc.)? If QoI we should get some more implementation feedback to see
> whether an explicit cancel is required.
>
> @mwatson2 <https://github.com/mwatson2> IIUC your proposal is 
similar to
> the reader view in e.g. Safari: an icon in chrome is lit when the 
web
> content is identified as an article. Also used for discovering RSS 
feeds
> back in the days when RSS was a thing. If so, you should redirect 
your
> comment to [3].
>
​No, I was just pointing out what I understand to be the most common 
use
case under the "flinging" category: you are viewing content in a web 
page
and there is an icon which lights up when there is a device available 
to
which the content can be "flung". The icon light up / dims as the 
remote
device(s) comes and goes. cf Cast, AirPlay etc.​

[1]
> 
https://lists.w3.org/Archives/Public/public-secondscreen/2015Apr/0079.html
> [2]
> 
https://lists.w3.org/Archives/Public/public-secondscreen/2015May/0005.html
> [3] #26 <https://github.com/w3c/presentation-api/issues/26>
>
> —
> Reply to this email directly or view it on GitHub
> 
<https://github.com/w3c/presentation-api/issues/81#issuecomment-100826159>
> .
>


-- 
GitHub Notif of comment by mwatson2
See 
https://github.com/w3c/presentation-api/issues/81#issuecomment-101866750
Received on Thursday, 14 May 2015 00:46:25 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 14 May 2015 00:46:25 UTC