Notes

Use Content-Encoding: gzip, only if Accept-Encoding: gzip

HTTP/2.0

In flavor of HTTP/2 "push" mode (draft-ietf-httpbis-http2-17 - Hypertext Transfer Protocol version 2 - 8.2. Server Push)

We ultimately decided to scrap resource packages in favor of HTTP pipelining and spdy, each of which gets you most of the speedup you'd get with packaging but doesn't require changes to web content. — 681967 – Web packaging format

An possible use of Service Workers (replace Application Cache/Cache Manifest) with FetchEvent

Service Worker as proxy

Use regular URLs

Defining bundles location can be required:

<link rel="assetbundle" src="/assetbundle.zip" ...>
<link rel="cache" type="application/zip" href="small-files.zip">
<link rel="resource-package" type="application/zip" href="site-resources.zip">

message/http with a body that is Multipart MIME

Or multipart/form-data or multipart/mixed

http://someplace.com/somearchive.tgz!/myimage.png

For unsupported browsers load the full URL where supporte only archive

MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="|||"
--|||
Content-Type: image/gif
.......(base64).....
--|||--

Serialized JavaScript

App manifest

  • https://github.com/meryn/parse-appcache-manifest/blob/master/src/parse-appcache-manifest.coffee

Last updated