- From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Jun 2016 08:32:40 +0000
- To: public-secondscreen@w3.org
I would caution against changing the resource selection algorithm, that works by picking the first source that works, and doesn't ever switch once playback is in progress. In particular it doesn't ever look ahead or do any scoring to pick a best resource. (Note that this is different from how `picture` works, which also has `source` children.) You will also have sites that don't use `source` elements but instead use `canPlayType` to set the source, and they would need some API to achieve the same thing. I guess the problem is that we might be playing using MSE locally, but the remote isn't a browser at all and instead uses DASH or a plain URL? I suppose what is needed is more information about the remote in `RemotePlaybackAvailability` so that an alternative resource can be provided in `connect()`? Whatever the API looks like, there will be fun questions like what to do if the remote resource has a different duration, or if it doesn't have the same set of tracks as the local one. -- GitHub Notification of comment by foolip Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/7#issuecomment-222927470 using your GitHub account
Received on Wednesday, 1 June 2016 08:32:43 UTC