<METAARCHIVE's and metasouces

The purpose of this mail is to serve of general utility, as for me would if implemented:

Objective:

    Download more efficiently web pages, especially applied to images.

A generic way:

    Join images in an only archive, (JAR or CAB or XYZ type, is not my problem).

A server/browsers way:

    Serve/capture an archive that contains multiple ones, that form part of that page, and in the browser part decompress and "untar" them.

An HTML especific way:

    <metaarchive id="mysource" src="/jars/thissitegeneric.jar">
    ...
    ...
    ...
    <img metasrc="mysource$image1.gif" src="/images/image1.gif">
    <img metasrc="mysource$image2.gif" src="/images/image2.gif">
    <img metasrc="mysource$image3.gif" src="/images/image3.gif">
    <img metasrc="mysource$image4.gif" src="/images/image4.gif">
    <object metasrc="mysource$java:Bobbles.class" classid="java:Bobbles.class" codetype="application/java">

Or using metaobject (perhaps more standard compliant, in the lexical pow:)

    <metaobject id="mysource" codebase="http://my.cabs.provider/cabinets/" archive="foryourweb.cab">
    ...
 
Observations:

    The non capable browsers don't see metasrc attrib nor metaarchive tag, so they simply dowload the normal way with src as server way path. Capable browsers parse the archive to find metaarchive tag, and if exists, apply them where metasrc is the virtual source in the uncompressed "untared" by browser jar way.If metarchive is a broken link or can't find a concrete archive in the compressed, try with src as traditional, that is, way non capable browsers do.

Greetings, igjav