> -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Bennett > Sent: Dienstag, 6. April 2004 02:37 > To: [EMAIL PROTECTED] > Subject: Re: Avalon Framework Diagram > > J Aaron Farr wrote: > > http://www.jadetower.org/muses/images/avalon.png > > > > Well? > > > > --- > > jaaron <http://jadetower.org> > > Should probably add a database block to the facilities section. I think > the plan is to have a low-level embedded database server and connection > pooling facility, that an object persistence layer (i.e. Hibernate) can > ride on top of that can supply us ultimately with facilities for > *entity* components. > > I don't know, maybe you want to lump all this together as a block > labelled "Persistence" under the facilities section. >
I don't know in which context the picture should be used. But we should stay in one abstraction / detail level. If you want to add persistence, you also should probably add things like security (subject- and code-level), presentation, workflow etc. We also should have a very clear consensus, on how those services are plugged together. To the drawing itself: I think the drawing could express more of the power of the Avalon container. One should see, that 'facilities' are also pluggable components and that that the 'framework' is the container, which gives the contract between the two component types: application components / blocks and facilities. A very initial picture could look like this: http://www.merlin.softwarefabrik.biz/docs/avalon/architecture.html Andreas > > --------------------------------------------------------------------- > 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]
