There are multiple ways to encapsulate heterogeneous data in documents: application resources (the "res" URL scheme), file archives (jar, zip, shar, tar, whatever). Of those possibilities, MIME is most Web-friendly IMHO, although the downside is that the transmitted resource grows. This should not be a problem for small resources and using it for big resources does not gain you anything, so you just get it as a separate file. And, as has been previously discussed, "jar" is not a protocol, it is a content type.
Chris _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert O'Callahan Sent: Wednesday, October 29, 2008 8:36 PM To: Kristof Zelechovski Cc: whatwg; Nils Dagsson Moskopp Subject: Re: [whatwg] video tag : loop for ever On Wed, Oct 29, 2008 at 11:35 AM, Kristof Zelechovski <[EMAIL PROTECTED]> wrote: Multiple AUDIO elements require one request per element unless they refer to the same stream or they use the data URL scheme, or the whole page is packaged as multipart/mixed, which would indeed be nice for such sets of small resources if only user agents supported it. This is a great use case for the "jar:" protocol.
