I am sorry ... I am about to sumerge myself deep in to the coding ...have mercy with a Merlin junior like me. I know that when you get the first sample you will get excited about it ... because is not only challenging but very powerfull in terms of distributed team develoment ...


the next message will be a study case with a apecific implementation.

I intend to use the injection/phased capability of Merlin to instanciate components.

My idea is to develop a wrapper, that should be the same for every component.

The wrapper can be either two things depending on its descriptor data:

- a proxy that talks to the tree on the remote merlin machine
- a file transfer/instanciator of the tree on the merlin machine

When a new deveoper registers him self with a tree, he should specify its location and initialization mode (remote or local) ... and thats all is required.

Other parameters could be which data has to be leased and how frequently it should be updated.

After this the developer will have the impression that he has been working locally, hopefully without noticing that perhaps the tree is been tested on the target machine (like the ultime x programming ... test and test and test and test again ... this time without being aware when)

Of course every tree would need a status telling in which phase of development it is. So the central tree can reject an automatic deployment in case of an undesirable status.

I hope I can get down to code next time. This is pretty much what I want to do.

Saludos
Maquina

From: Niclas Hedhman <[EMAIL PROTECTED]>
Reply-To: "Avalon framework users" <[EMAIL PROTECTED]>
To: "Avalon framework users" <[EMAIL PROTECTED]>
Subject: Re: Working from home and docking
Date: Tue, 19 Oct 2004 03:51:43 +0800

On Tuesday 19 October 2004 03:40, Samuel Ferrer wrote:

> ... I see that this is a sensitive subject and is taking too long ... I
> would drop it and focus on something everybody agrees is really needed.

That is not the case. :o)

I am just trying to figure out what you are trying to do.
You are far too abstract and/or leaving out too much details for me to get the
picture.


Please, talk in terms of Java classes, object instances, configuration files,
persistence stores or something else more tangible for a poor fellow like
myself.


Providing MIR as an example of 'docking' doesn't help. I could be docking
source code, class files, Jars, blocks, live instances, and possibly other
things.

Cheers
Niclas
--
   +------//-------------------+
  / http://www.bali.ac        /
 / http://niclas.hedhman.org /
+------//-------------------+


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]


_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.com/



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to