And yes, we did use Jini to manage the components and their security across nodes. There are a few services that use Jini to manage cache, state, and messaging across JVMs, even if they are on the same physical server. The nice thing there was that by using smart proxies we could have a service, or a cache between a pool of JVMs on a single host (because they can and will disappear) with the same effort and management across multiple servers.
The MD5Url for loading in versions of components that I mentioned earlier comes from the newer releases of Jini.
There's some pretty cool stuff out the there to look at and borrow ideas from.
Cheers, Thor HW
On 25-Mar-04, at 3:23 PM, Pier Fumagalli wrote:
On 25 Mar 2004, at 19:40, Thor Heinrichs-Wolpert wrote:
Hmmm ... I've never used JMX for remote loading as the security just isn't there for my tastes and there other mechanisms that work so much better. It does do a fine job of loading/unloading components though.
Gianugo and I spent an hour on the phone (he paid the international rate :-) talking exactly about it...
He has a lot more practical experience on JMX than I have, and I believe that we got down to a pretty good rationale on how it can all work...
Gianugo, would you do the honors (as you are more experienced than me in this field) to summarize what we chatted about this evening?
Pier
