The full revised specification can be viewed here.
http://mfoltzgoogle.github.io/presentation-api/
m.
On Thu, Sep 11, 2014 at 5:16 PM, mark a. foltz <mfoltz@google.com> wrote:
> I have created a pull request that conveys the suggested specification for
> automatic session reconnection.
>
> https://github.com/webscreens/presentation-api/pull/23
>
> Please note that there are some open issues that were added as I fleshed
> out the specification:
>
> * If more than one presentation session exists with the same url and
> presentationId (on different screens) then what is the behavior of
> joinSession(url, presentationId)?
>
> * If the user agent becomes aware of a presentation session after the page
> has already called joinSession, there is no way to notify the page of its
> existence. Should we use an event handler instead?
>
> * If the page calls startSession(url, presentationId) with the same url
> and presenationId as joinSession(url, presentationId), and the latter call
> has not resolved, behavior is not defined.
>
> * Since we permit multiple opener pages to connect the same presentation
> page, we need to define how connection and disconnection of these pages is
> communicated to the presentation page (if at all).
>
> I'll open these up for discussion, perhaps we can resolve some of them to
> make the spec more solid.
>
> m.
>
>
> On Wed, Sep 10, 2014 at 1:41 PM, Jonas Sicking <jonas@sicking.cc> wrote:
>
>> On Wed, Sep 10, 2014 at 11:47 AM, Anton Vayvod <avayvod@google.com>
>> wrote:
>> > I think Jonas suggests using Promises in his reply to the thread.
>>
>> Yup!
>>
>> / Jonas
>>
>
>