519
edits
Difference between revisions of "Zimit"
Jump to navigation
Jump to search
→Player
(→Player) |
(→Player) |
||
| Line 20: | Line 20: | ||
* the SW is installed on the welcome page. If any page is loaded and the SW still not loaded, a redirection to the homepage will happen to load the SW and then automatically come back to the original page. Do achieve to do that, each page HEAD node is modify to insert the appropriate piece of Javascript at the time of the warc 2 zim conversion. | * the SW is installed on the welcome page. If any page is loaded and the SW still not loaded, a redirection to the homepage will happen to load the SW and then automatically come back to the original page. Do achieve to do that, each page HEAD node is modify to insert the appropriate piece of Javascript at the time of the warc 2 zim conversion. | ||
* In the reader | * In the reader Wabac.js, there is only one specific part related to ZIM content structure and this is in "RemoteWARCProxy". This part knows how to retrieve content from the specific ZIM storage backend. For the rest the code is the same as before. | ||
* Regarding URL rewriting itself, we have two kinds which are both data-drivent: | |||
** The static URL rewriting which is done with Wombat | |||
** The Fuzzy matching which is done within the ServiceWorker | |||
* The URL rewriting is done at two levels: | |||
** When the javascript code calls specific Browsers API, these calls are superseeded and ultimatively call Wonbat | |||
** When a URL is called, then it goes through the service-worker which does the fuzzy-matching and the URL rewriting. | |||
== Source code == | == Source code == | ||