![]() ![]() Because Readium LCP is designed by publishers, it has some intuitive features that make it an attractive choice for ebook DRM. ![]() In other words, it doesn’t play favorites with ebook distribution or device it is designed for the author and publisher by publishers. Because of the aforementioned performance issues, development effort was never spent to implement this functionality. Readium LCP is an open-source DRM solution developed specifically to be vendor-neutral. So, to solve this problem, the MO engine would need to query a single audio file URL (on the fly, as defined by the SMIL files), pointing to a resource that is in fact located inside the zipped EPUB container. Now the books you purchase or download on one device will appear automatically across all the devices you have ADE on. The audio files are not actually preloaded by the readium-js document “fetchers”, simply because HTML documents do not reference these audio files (instead, the SMIL files do). The problem specific to Media Overlays is that audio files are loaded dynamically by the MO playback engine (which code is in readium-shared-js). Normally, the webview loads assets in a much smarter way, especially audio and video media (on-demand, incremental pre-fetching, loading, etc.). This is called “programmatic” fetching in the source code. readium-js EPUB core processing engine written in Javascript. You will see in readium-js document “fetchers” that when loading a packed / zipped EPUB, all the resources attached to an EPUB HTML file are statically loaded into “binary blobs”, which then replace src attributes in the HTML markup (using Blob URIs). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |