----- Original Message ----- From: "Peter Donald" <[EMAIL PROTECTED]> To: "Avalon Development" <[EMAIL PROTECTED]> Sent: Saturday, September 29, 2001 10:11 PM Subject: Re: DeployMonitor/Manager for Phoenix
> On Sun, 30 Sep 2001 11:56, Mircea Toma wrote: > > Hi Peter, > > > > I have done some coding but I want to confirm with you if this is the > > direction you want to go?! > > Looks good. One question though - wouldn't be easier to have the interface > use file objects directly rather than using URL objects that are required to > be files? 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?! Mircea > > I attached the new classes to give you an idea > > about what I've done. It seems that having a basic implementation for > > "org.apache.avalon.excalibur.vfs" package would make the code much cleaner! > > Yup. I actually have a basic implementation somewhere around ... I will try > to finish fixing it up and check it in ... though it could be a while before > I get a chance ;/ > > -- > Cheers, > > Pete > > Duct tape is like the force. It has a light side, and a dark side, and > it binds the universe together ... > -- Carl Zwanzig > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
