A DESCRIPTION OF THE REQUEST :
We have a webstarted conferencing application which we produce the signed jars for, but which may be distributed by us, through one of our web server (codebase) or could be distributed by any of a number of server customers, through their own web servers. The application is not different, the jar signing and versions are common, but the codebase uniqueness means that each web server will cause a fresh instance of the the jars to be downloaded and maintained.

It would significantly reduce downloads, as people may switch from one server to another (one conference to another), if there were a way to specify the specific (physical) codebase instance, but to attribute it to a common codebase URL (logical codebase). That would mean that our customers could specify their server as the real codebase, and server jar files from there, but by attributing it to our logical codebase, would not require a download if the logical codebase folders in the cache already contained the jars.

I recognize the need to preserve security, thus this feature should be able to access the signing and versioning of the jar, to verify the originator. This may entail servlet support to access this information.

JUSTIFICATION :
Significant decrease in superflous downloading and perceived commonality of the code.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
A logical codebase argument in the jnlp element.

<jnlp spec="1.0+" codebase="http://xxx1.yyy.com:83/dev/jars" commonCodebase = "http://xxx.yyy.com:83/dev/jars" >


ACTUAL -
Each codebase instance generated a new cache hierarchy and requires a download.