Hello, Your "A" strategy will be easily implementable using the proxy-cache Proximity (the new one, NOT the currect RCx tree). You need a new "router", based on an existing one.
See the http://trac.abstracthorizon.org/proximity/wiki/Release_2 "Architecture" link. All you would do is the following: simply subclass the group-based repository (or repo-based, as you like) and override the single doRetrieveItem method, to behave as you said: do super.doRetrieveItem and if fails, retry it without classifier, sign it, store it, and return it. Also, the router could use the classifier as "key selector". It could act as "plain" group-based (or repo based) router for requests without classifiers. The release of Px2 will replace the RCx line, but is a little delayed. The core (as it is written on wiki and much more) is already implemented and Web frontend is still in development. Hope helps, ~t~ On 5/6/07, DavidCorbin <[EMAIL PROTECTED]> wrote:
A) in a caching-proxy repo, when asked for a jar with classifier "signed-by-foo", it returns the one it has, or it signs it on the fly, caches it and returns it.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
