-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hello,
> Actually, the proposal would be a package with a manifest, then you
> address the images normally and they get loaded from the package in
> browsers that support it (and one by one from the web server in ones
> that don't). That way it's even backwards compatible and can be rolled
> out as soon as desired. See http://limi.net/articles/resource-packages
> for a very initial proposal draft; comments welcome.
I don't understand why you discarded multipart MIME so early...
It would be very easy to implement (most eMail client do it already), it
feels less like a 3rd-party application and more integrated into HTTP.
Compression could work transparently as it does today, and it would
allow more interesting uses:
- - real attachments to websites, like emails. For example, the home page
could attach the stylesheets and images, which speeds up loading even
more since in one request you get everything without having to parse the
page first. Other pages would refer to the files as usual, the browser
would use the cached versions, or if you didn't visit the home page
first, load them as needed. (Of couse, people would soon start attaching
everything to every page...)
- - no more need for "meta refreshing" on nice download pages: have the
"your download is starting now" message first, and the file to be
downloaded second in the multipart message.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iQEcBAEBCgAGBQJKnUKJAAoJEIplHwrShYbrCekIAK6ZnRNKllcs4UBZmFLOcEl2
/aMaIPF+JF3iAAyONm9+03S9y+9FgSIO4S1GwKZ2zWxggzIHle0w9QwVLhlb/gVZ
RZiqgi5/R7ZJi9532xyQCG8hRnjCHwMkfRZIRi/A429cSqA5gM3jpuS/bfiMTIvi
euwE+TSxVhlk21bCyRiVaaZNggG5HQMoOiDcIYQGUnG3QZu5bm/79f3DY22vVIJw
EadsyfscQ0+cKwseglsHlztx59XSp3I2ksA9K7SEQQyNCsQFPqYK3ZPh0UBH0eS1
BMdwZvctc/juhdTK7nkHaUgju4XHgX54WsPKQwjPA5gQlqKJ/ex9aYMT5kFKzgI=
=mash
-----END PGP SIGNATURE-----