-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Partial offline support #873
Comments
At a glance, it seems like a great idea! In particular because of the lack of availability of persistent license support and because of the incredibly low bandwidth requirement for licensing. Let us know if you have any questions as you work on the PR. My gut instinct is to either add a parameter to Thanks for the suggestion, and for offering to contribute! We really appreciate it. |
Cool! My current work adds a The default being true. |
I changed my approach to an extra param for Here is what the changes currently look like, along with current naming scheme: https://github.com/google/shaka-player/compare/master...indiereign:offline-data-online-license?expand=1 I am about to look into updating and adding tests but would appreciate feedback on current approach as well. |
I took a look and left some comments. In short, I think configuration is better in this case. I can't see any reason you would need to change that flag per-asset, and if you need to, you still can through Thanks again for working on this! |
Yep, got a barrage of emails :). |
Okay, sounds good. We can continue discussion on the PR. |
Reopening. Just noticed that we didn't update the configuration structure definition to include the new flag. I'll fix it shortly. |
I am also renaming the option from |
OK, are you doing that, or do you want me to submit another PR? |
No, I'm taking care of it real quick. Sorry about that. I should have noticed these things before merging. :-) |
I have had a look into offline support in shaka player 2.1.3 and noticed that it really only applies (currently) in ChromeOS.
I have had a tinker in
storage.js
and with a custom ManifestParser to get a partial offline scenario working where the content is downloaded but the license check to the remote Uri still occurs.This would help out people who can pre download the content before traveling to a place with terrible/metered internet (hotels).
Would you accept a PR or discussion for this? I am in the middle of a POC for it, but the main chokepoints of change are:
storage.js:301
(where storage initialises the drmengine with a hardcodedisOffline=true
parameter)storage:425
(same as above)I think what I want is to tell the storage api that I still want a temporary license (instead of it forcing a persistent-license (which has the flow on effect in drm_engine of checking the persistent-license session type).
Good idea / bad idea?
The text was updated successfully, but these errors were encountered: