On Sun, 30 Sep 2001 15:49, Mircea Toma wrote: > I was thinking of using multiple 'baskets' ( ./apps like directories) and > monitor them all even if they are remote locations ... F.S. of course. I > think I know how you see the remote loading + hot deployment done: the > DeploymentManager will monitor only the ./apps directory and if an > application has to be loaded from a remote location it will be done on > demand using Deployer.deploy(..) downloading the application into the > ./apps directory thus deploying it?!
I was thinking of downloading it into a ./cache directory but the ./apps directory works aswell - however you would have to make sure that there was no name clashes (ie a remote .sar could not overide a local .sar). And you would also want to make it possible to clean the cached versions out every now and again. Hmmm ... I just had another thought. See what you think of this. In the other JMX and redux thread I mentioned that one option was > 7. Enhance BlockContext and/or assembly descriptor so that Blocks can be > marked as "privlidged" which means they get access to the kernel interfaces > ... including MBeanServer Now lets say we had a Block that had access to the Deployer interface. In this case the Monitor could actually be implemented as a .sar because it could monitor the directory and then call the Deployer kernel component. -- Cheers, Pete ----------------------------------------------- "Only two things are infinite, the universe and human stupidity, and I'm not sure about the former." -Albert Einstein ----------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
