cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clark C. Evans" <clark.ev...@manhattanproject.com>
Subject Re: Parallelizing Cocoon Development
Date Fri, 24 Dec 1999 16:20:16 GMT

Component based programming is always a win.
Looks like you've found two attitudes for a
component:

(a) A component *as* a tool to be administered.
(b) A component *as* a tool to doing work.

Perfect.

Clark

On Fri, 24 Dec 1999, Stefano Mazzocchi wrote:
> In Avalon, we introduced the "block" design pattern. A block is a black
> box that have two painted sites: one to do the work, one to be
> administered.
> 
>              +--------+
>  work ---->  |        |  
>              +--------+
>                   ^
>                   |
>                 admin
> 
> 
> The working interface is not mandated, it could do anything. The admin
> interface is a mix of patterns like Configurable, Composer, and such.
> 
> Avalon was created to allow you to design your application in a
> "block-oriented" way, rather than "object-oriented" way. A block is a
> collection of classes that work together to give a service exposed thru
> an interface to the rest of the program.



Mime
View raw message