Re: Google/Mozilla Presentation API update

On Wed, Aug 20, 2014 at 5:10 PM, Mark Watson <watsonm@netflix.com> wrote:
>> > Regarding restarting sessions, don't the proposals suffer from the same
>> > problem of available device detection that the original API suffers from
>> > ?
>> > That is, the onavailablechange event is indescriminate and even if it is
>> > fired a call to requestSession may fail (no available devices / sessions
>> > matching the parameters to the requestSession call). This corresponds to
>> > a
>> > UX where the "present" icon is shown, but clicking it results in a
>> > failure.
>> > There's no need for this bad UX, because we know, before showing the
>> > icon,
>> > everything we need to know to make it more accurate.
>>
>> No. The page would simply call requestSession() with resumeOnly set to
>> true before displaying any UI. If the connection succeeds the page
>> would display the "connected" UI rather than a "present" icon. If the
>> connection fails, then it would show a "present" icon (unless the
>> onavailablechange fires again and lets the page know that the TV is no
>> longer available).
>
> I can see how that works, but what if the site doesn't want to automatically
> reconnect ? Suppose the presentation id has been shared across a bunch of
> devices but the application model is that there is only one active
> controller at a time ? Reconnecting would correspond to wresting control
> from the existing controller, which the user might not want.

Then don't call requestSession() automatically and instead display a
"present" icon.

I guess I'm not sure what experience you are trying to archive.

/ Jonas

Received on Thursday, 21 August 2014 00:19:39 UTC