- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Apr 2016 23:33:23 +0000
- To: public-secondscreen@w3.org
> Or is the presentation identifier meant to be only known by the controlling user agent and not passed around to the receiving user agent at all? The current spec does pass the identifier from the controller to the receiver [1]. Since additional controllers need the same identifier to reconnect it seems like the same identifier will get used for all connections? There is an issue you note with different receiving contexts within the same receiving user agent ending up with the same presentation URL and identifier. In fact, it looks like the method of generating the identifier was dropped from the "starting a presentation" algorithm. If we defined it to almost-guarantee uniqueness of the identifier, it would seem to address the issue. One problem with having the receiver generate the identifier: we won't be able to resolve a new PresentationConnection on the controller in a "connecting" state, since we don't yet have the identifier from the receiver. [1] https://w3c.github.io/presentation-api/#monitoring-incoming-presentation-connections -- GitHub Notification of comment by mfoltzgoogle Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/253#issuecomment-211631230 using your GitHub account
Received on Monday, 18 April 2016 23:33:25 UTC