You are viewing a plain text version of this content. The canonical link for it is here.

Posted to docs@cocoon.apache.org by do...@cocoon.apache.org on 2004/12/07 14:22:36 UTC

[Cocoon Wiki] Updated: Blocks

   Date: 2004-12-07T05:22:35
   Editor: PaulRussell <pr...@apache.org>
   Wiki: Cocoon Wiki
   Page: Blocks
   URL: http://wiki.apache.org/cocoon/Blocks

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -91,6 +91,8 @@
 Blocks are not active nor passive. Just like electronic chips, they are useless by themselves, but provide functionality if properly connected with an external system. This is not the behavior of engines, for example, which are active by themselves. Calling them components would create conflicts. Blocks are used by some Avalon containers. There is a potential conflict here, but there is also potential overlap (it could be possible, in the future, to install an Avalon Block in Cocoon) so the use of the same name is justified. 
 -- stefanomazzocchi
 
+Have people considered using something like HiveMind as the infrastructure for supporting blocks, rather than 'rolling our own'? I don't see that we'd need to build much (if anything) on top of it, and it would be seriously elegant: installing a block is a case of dropping it in the 'lib' directory of your .war file. I'd be more than happy to assist in making this change, although I'll need to get back up-to-speed with cocoon first!!
+-- [PaulRussell]
 ----
 
 === Related technologies and projects ===