- From: Mounir Lamouri via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Jan 2016 14:21:52 +0000
- To: public-secondscreen@w3.org
I guess what we do while `connecting` is going to be tightly related to what we do with regards to media commands while `connecting`. We need to offer a good developer experience. I would suggest the following: * While the remote state is `disconnected` or `connecting`, the media commands (ie. `play()`, `pause()`, etc.) go to the local playback. * When the state is `connected`, the media commands go to the remote playback. * When going to/from `connected`, we switch from local to remote playback. When switching playback, the new playback inherits from the state of the previous playback (ie. if it was playing, it keeps playing from the same position). The playback being switched from will be paused. If we specify that, it will allow a decent default behaviour: when `connected`, the local playback will stop, and the remote playback will start from the same position. Otherwise, while `connecting`, the local player will be allowed to pause, show a spinner and play the remote player when it is `connected`. WDYT? -- GitHub Notification of comment by mounirlamouri Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/3#issuecomment-175653724 using your GitHub account
Received on Wednesday, 27 January 2016 14:21:54 UTC