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 2005/01/09 22:59:41 UTC

[Cocoon Wiki] Updated: BlockImplementation

   Date: 2005-01-09T13:59:41
   Editor: MarkLundquist
   Wiki: Cocoon Wiki
   Page: BlockImplementation
   URL: http://wiki.apache.org/cocoon/BlockImplementation

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -13,8 +13,8 @@
 
 For this reason, the block wiring information should be located in a configuration file that is "read-only" by cocoon and "read/write" by the block deployer.
 
-{{{   +--------+                          +----------------+
-   | cocoon | <--- [File System] <---> | block deployer |
+{{{   +--------+                          +----------------+
+   | cocoon | <--- [File System] <---> | block deployer |
    +--------+                          +----------------+}}}
 
 Note that the block deployer *could* be anything (a CLI, a webapp, an eclipse plugin). The above meets our second requirement: user friendlyness for all types of users.
@@ -27,21 +27,21 @@
 
 The block deployer architecture is the following
 
-{{{           +--------------------+     +------------------+
-           | +-----------+      |     |                  |
-  [FS] <---->| FS Driver |      | <-> |  User Interface  |
-           | +-----------+      |     |                  |
-           |                    |     +------------------+
-           |      block         |
-           |    services        |
-           |                    |
-           |  +---------+       |
-           | +---------+|       |
-           | | Locator |+       |
-           | +---------+        |
-           +------^-------------+
-                  |
-                  V
+{{{           +--------------------+     +------------------+
+           | +-----------+      |     |                  |
+  [FS] <---->| FS Driver |      | <-> |  User Interface  |
+           | +-----------+      |     |                  |
+           |                    |     +------------------+
+           |      block         |
+           |    services        |
+           |                    |
+           |  +---------+       |
+           | +---------+|       |
+           | | Locator |+       |
+           | +---------+        |
+           +------^-------------+
+                  |
+                  V
              block library}}}
 
 which is composed by four main parts:
@@ -73,5 +73,5 @@
 
  1. the sitemap interpreter: to find out where the blocks sitemaps are mounted in the main sitemap URL space
  1. the block: protocol: to locate the services provided by the blocks
- 1. the component manager: to locate components provided by the blocks (either avalon components, sitemap components and virtual components)
+ 1. the component manager: to locate components provided by the blocks (either avalon components, sitemap components and VirtualComponents)