-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Meta] Write document describing protocol requirements #1
Comments
@mfoltzgoogle What do you think about considering "guest mode" (Allow users not in the same network to present on the screen) in the requirements? |
@louaybassbouss Sorry for missing #1 (comment) earlier! According to the charter for the community group [1], support for displays outside the controller's local area network is not in scope, so I don't think we can list guest mode as a requirement. However I don't think it's a problem to hypothesize whether a given transport would be possible to use over a WAN without diving into a specific mechanism. After all the protocol may be extended to support this case in the future outside the scope of the CG. Filed Issue #41 for guest mode considerations. |
thx @mfoltzgoogle agree with you this out of scope. But now we have a new issue #41 for this we can discuss there if this is a relevant feature or not (low prio). |
Closing out this old issue, discussion of Guest Mode can continue in #41. |
This issue will be used to track work items to author a consensus requirements document. This will help guide discussion whether protocol features are in scope or out of scope, and to evaluate the suitability of technology choices.
The requirements flow primarily from three sources:
Starting points are the draft requirements for the community group recharter [3], along with the slide deck I presented at TPAC 2016. I can simplify these and put them into a PR to start this work item.
[1] https://w3c.github.io/presentation-api/
[2] https://w3c.github.io/remote-playback/
[3] https://github.com/webscreens/cg-charter/blob/gh-pages/requirements.md
The text was updated successfully, but these errors were encountered: