View on GitHub

PortableCache

Cache assets, reduce downloads, load faster.

What is PortableCache?

PortableCache is a small library for mobile web developers winning better performance. Enables you to cache arbitrary resources (js, css, img, etc) in static storage and reduce server request.

Bonus points:

Who should use it?

Unlike AppCache, PortableCache can:

Examples

Example Codes

Visit Example codes page on GitHub Wiki.

Demos

PortableCache

Simplest example of using declarative API, lazyload and responsive images.

Web Audio Drumpad

Imperative API usage example. Audio sample data are imperatively cached and used as drum sound. It is a good example of deferred AngularJS (1.0.0~) bootstrap. Works on Chrome, Safari and Firefox.

Quick Start

You can quickly try out PortableCache by following 3 steps.

  1. Insert following meta tag to your existing project's head tag.
    <meta name="portable-cache" content="version=20131228">
  2. Insert script tag to load portable-cache.js (Make sure it is below meta[name="portable-cache"]).
    <script src="js/portable-cache.js">
  3. Replace attribute name of resources you'd like to cache with data-cache-url.
    <img src="img/image.jpg">
    <img data-cache-url="img/image.jpg">

Installing PortableCache

PortableCache is available thorugh bower.

bower install PortableCache

You can of course clone from repository.

git clone git@github.com:agektmr/PortableCache.git

Size (as of 0.7.3)

APIs

Visit APIs page on GitHub Wiki.

Browser Support

Following browsers are supported by PortableCache.

Following browsers are confirmed to gracefully fallback on PortableCache

Need tests on following browsers

Browsers not listed here are yet to be tested.

FAQ

When exactly is pcache-ready event called?

PortableCache bootstraps loading link tag and script tag first. pcache-ready event fires after all link tags and script tags (except ones with async attribute attached) are loaded and executed.

What happens if storage's quota exceed?

If quota exceeds on user's browser, PortableCache will simply give up storing cache and fallback to use remote resource. But some browsers request permission for larger quota to users. On any of those browsers, PortableCache will handle gracefully and continue using storage if granted.

How do I separate cache version per URL path?

You may notice version string you have assigned to a website is tied to the entire host, potentially overwriting same host's other apps' versions which is path separated.
For example, you have an app on
http://example.com/app-a/
Then you create another app on
http://example.com/app-b/
In this case, whichever app user opens will overwrite the other app's version string.

You can avoid this by giving root-path to meta[name="portable-cache"].

<meta name="portable-cache" content="version=20130110, root-path=/app-a">

This way, the version string is tied to the app path rather than the entire host.

Can I use lazyload / responsive image features without caching?

Absolutely. Just set data-cache-version as an empty string. PortableCache will simply use remote resource URL with lazyload / srcset features left available.

<img data-cache-url="img/image.jpg" data-cache-srcset="img/image-320.jpg 320w, img/image-640.jpg 640w, img/image-640.jpg 320w 2x" data-cache-version="" lazyload>

Can I detect unsupported browsers on server side?

You may wish to remove PortableCache if a browser is known to be unsupported.
You can use a version string stored as pcache_version in cookie which
PortableCache sends. If a browser is already proved to be unsupported (fallback without caching), it carries a string NOT_SUPPORTED instead of a version string. Catch this cookie on your server so it can serve an HTML without PortableCache to avoid JavaScript parsing overheads.

Author

Eiji Kitamura

+agektmr, @agektmr