This is a plugin that I'm proposing to develop.
I think it can, and here's how: establish a convention as to how to interpret specific parts of the url.
For context, let's say a web site uses jquery, and they have a "compressed" copy on their web site called "jquery-1.6.2.js".
A well known means of identifying something uniquely is with a UUID, or universal identifier, so just by picking one, say 57898435-a110-4620-8280-37c07357b513, and making it part of the url, you would allow the following parts to specify the "item" (jquery) and the version (1.6.2), as in
That's all that's needed to allow browsers to identify this entity uniquely and to use a local version in preference to the one available on the web server, say with extra debugging, or more limited features.
One could use such a scheme to avoid having to download the file completely and provide equivalent functionality with a plugin, something I plan to do.
Providing the name and version in the url avoids this.