Re: httpmd

Gregg Wonderly wrote:

> It occurs to me that we could devise a versioning solution with code in the
> RMIClassLoaderSPI implementation to annotate the codebase URL with
> versioning
> info (MD5 sum, or just date, time and length info as a hash) as an
> ignorable URI
> component which the web server(s) would ignore, and still just serve up the
> associated file.

Gregg,

Using the query part of a URI could indeed be an interesting part of the
Request URI to contain additional meta data that could be utilized by
some parts in the infrastructure. However I don't think all those URIs
can or should point to the same file, as your clients somewhere on the
network can rely on a particular content of the JAR file. I would expect
the query part to be relevant for the content being served as well and
if that is the case a plain out of the box webserver is not going to
tackle this.

E.g. controlling class boomerangs at the server side is possible because
a server can keep track of all the codebase annotations it served during
its lifetime. However class loaders for clients can't do this because
they have no knowledge about the evolution of these codebases, but what
if the query part containing the meta data of the URI could help
RMIClassLoaderSpi deciding that when code arrives it actually matches an
already existing classloader even though the associated URI differ
partly. I have no clue however of the implications of this all :-)
--
Mark

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]