avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcus Crafter <craft...@fztig938.bank.dresdner.net>
Subject Re: tweety: educational avalon container
Date Thu, 20 Jun 2002 10:53:51 GMT
Hi Leo,

On Wed, Jun 19, 2002 at 12:16:00PM +0200, Leo Simons wrote:
> -------------
> Avalon Tweety
> -------------
> 
> Background
> ----------
> 
> Talking about the complexity of avalon and its associated learning curve
> made me draw a parallel with the complexity of unix. An approach that
> has worked there: "Want to learn how to program unix? Start with it's
> tiny brother - minix."
> 
> I think it'd be a good idea if we provide a minimalist container
> explicitly designed around educational value.

	Sure.

> Goals
> -----
> - be well documented
> - provide full support for the avalon framework interfaces
> - provide support for nothing else
> - use default framework implementations where possible
> - sacrifice flexibility for readable code wherever possible
> - sacrifice reusability for readable code wherever possible
> - use the most simple configuration possible
> - support only minimal metainfo (for example, no dependency mapping)
> - no security
> - minimal thread management
> - no classloader management
> - separation of engine and (mainable) embeddor
> 
> Use Case
> --------
> An example of an avalon container for simple components, to use in
> teaching avalon concepts.

	Sounds good. I think the effort will be well worth it. It would be
	good to also document somewhere answers/definitions to the fundamental
	questions like 'so what is a container anyway ?', 'what role
	does a container play in my system ?', etc. I'm not even sure I
	can fully answer these! :-) and I'm sure they'll come up on the
	user list in the future.

> ########################################################################
> # sample tweety.components file
> ########################################################################
> #
> # Use this file to specify which components you want tweety to manage,
> # and under what role they should be put in the ComponentManager.
> # FORMAT: <role> = <javaclassname>
> 
> HelloWorldServer = org.apache.avalon.demos.HelloWorldServerImpl
> HelloWorldClient = org.apache.avalon.demos.HelloWorldClientImpl

	What will the components do ? Send messages to each other printing
	out 'Hello world' or something ? (just wondering)
	
..<snip>..

	The technical details look fine to me, although I agree with
	Nicola Ken about using RMI, perhaps a single main() to start/stop
	everything might be simpler.
	
	Cheers,
	
	Marcus
-- 
        .....
     ,,$$$$$$$$$,      Marcus Crafter
    ;$'      '$$$$:    Computer Systems Engineer
    $:         $$$$:   ManageSoft GmbH
     $       o_)$$$:   82-84 Mainzer Landstrasse
     ;$,    _/\ &&:'   60327 Frankfurt Germany
       '     /( &&&
           \_&&&&'
          &&&&.
    &&&&&&&:

--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>


Mime
View raw message