You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
implement Node.js-specific network and storage adapter as a separate "w3c-cache-via-node-fs" project
worth extracting out "unique-filename-from-w3c-request" project, to be used elsewhere
provide an alternative "w3c-cache-via-cordova-file" project, for Cordova use
provide an alternative "w3c-cache-via-localforage" project, for browser use (LOW PRIORITY)
require the W3C cache object to be provided at runtime by consumers
possibly extract transformation work out into separate project
such a project would need access to the same Cache object in order to operate correctly
By focusing on interchangeable Cache implementations, we gain increased portability for the rest of the code (e.g. transformations, etc). Apps that need dynamic lookups can be written against the standard Cache API and will be more compatible with Service Workers in future.
The increased portability should help with construction of a "cordova-plugin-evergreen" project that can be used to safely update the contents of a Cordova app's www/ directory at runtime.
The text was updated successfully, but these errors were encountered:
jokeyrhyme
changed the title
slim redesign based on newer W3C specifications
redesign based on newer W3C specifications
Nov 11, 2015
Should consider the ramifications of switching to a different directory structure. Instead of scrambling filenames in order to keep output in a single-depth directory, what if we could preserve the directory structure of the original content somehow?
e.g. output_dir / origin / same / path / as / remote / resource.js
Ideas for a redesign:
By focusing on interchangeable Cache implementations, we gain increased portability for the rest of the code (e.g. transformations, etc). Apps that need dynamic lookups can be written against the standard Cache API and will be more compatible with Service Workers in future.
The increased portability should help with construction of a "cordova-plugin-evergreen" project that can be used to safely update the contents of a Cordova app's www/ directory at runtime.
The text was updated successfully, but these errors were encountered: