[presentation-api] Have the receiving browsing context generate the presentation identifier?

tidoust has just created a new issue for 
https://github.com/w3c/presentation-api:

== Have the receiving browsing context generate the presentation 
identifier? ==
In the spec, the presentation identifier identifies a receiving 
browsing context. To reconnect to a session running on some receiving 
user agent, all a Web app should need is the presentation identifier 
and the presentation URL. This allows to pass the identifier from one 
user agent to the other.

For this to work, the receiving user agent needs to know how to 
associate a presentation identifier with a receiving browsing context.
 I assume this means that the presentation identifier must be 
exchanged somehow between the controlling user agent and the receiving
 user agent.

However, right now, the presentation identifier is generated by the 
controlling user agent, which seems odd: no matter how unlikely, two 
controlling user agents could perhaps generate the same identifier for
 two contexts running on a receiving user agent, leading to possible 
confusions.

Wouldn't it make more sense for the receiving user agent to generate 
the identifier itself and pass it to the controlling user agent when 
the connection is established?

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?

Please view or discuss this issue at 
https://github.com/w3c/presentation-api/issues/253 using your GitHub 
account

Received on Monday, 1 February 2016 21:54:55 UTC