W3C home > Mailing lists > Public > public-secondscreen@w3.org > November 2014

Re: Allow page to designate a default presentation URL

From: Anton Vayvod <avayvod@google.com>
Date: Tue, 11 Nov 2014 16:02:29 +0000
Message-ID: <CAOjek6qAMboGgcfMc6GgVroKk=4hmd8eFcasBofuvwn1zC9fAA@mail.gmail.com>
To: "Kostiainen, Anssi" <anssi.kostiainen@intel.com>
Cc: "Bassbouss, Louay" <louay.bassbouss@fokus.fraunhofer.de>, "mark a. foltz" <mfoltz@google.com>, "public-secondscreen@w3.org" <public-secondscreen@w3.org>, "public-webscreens@w3.org" <public-webscreens@w3.org>
Hi Kostiainen et al!

On Tue, Nov 11, 2014 at 3:19 PM, Kostiainen, Anssi <
anssi.kostiainen@intel.com> wrote:
>
> Hi Louay, MarkFo,
>
> > On 11 Nov 2014, at 16:50, Bassbouss, Louay <
louay.bassbouss@fokus.fraunhofer.de> wrote:
> >
> > If I understand correctly, we need to extend the spec to let the origin
page receive the session created by the Browser?
>
> MarkFo - how do you see the session object delivered in a scenario where
the user initiates the presentation from the UA's user interface?

1) Through an uninitialized "presentation.default" PresentationSession
object? The UA can't initiate the default presentation until onstatechange
has a listener attached? Should we then set the default presentation URL
via the object rather than the meta/link tag? Then the page can actually
change the default presentation URL on the go.

2) Through a more generic event that would work for both page and UA
started sessions that the page could join? It could potentially be used
instead of the Promises for start/joinSession.

presentation.onsessioninitiated = function(e) {
  setSession(e.presentationSession);
};

>
> > Another question, how the origin page can pass a session id to join an
existing session?
>
> Does it make sense to scope this "implicit invocation" (throught the UA
UI) use case more tightly to new sessions only? For joining to existing
sessions, the programmatic API could be used.
>
> Are both the "implicit invocation" and the programmatic API attempting to
address the same use cases i.e. are we striving for feature parity between
the two? If so, it may cause problems since the programmatic API tends to
be more expressive by design.

If there's an existing presentation session going on, the page should be
able to find the presentation id itself (i.e. via the local storage) and
join the session without any user action. There's no need for the default
presentation URL in this case.

> what is the relationship between [1] and [3]?

The default presentation URL could be used by the UA to create a filter for
device availability.

>
> Thanks,
>
> -Anssi
Received on Tuesday, 11 November 2014 16:03:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:18:43 UTC