cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerhard Froehlich" <g-froehl...@gmx.de>
Subject RE: [RT] Avoiding Cocoon Thermal Death
Date Wed, 13 Mar 2002 17:55:46 GMT
Hi,

<skip agreed/>

>Ok, now I will describe how I see a cocoon block.
>
> a) Cocoon Blocks are Zip files. Even if less efficiently compressed,
>Zip archives have internal random-access features, unlike tar.gz,
>moreover they are easy to read/write within java and are used for both
>.jar and .war
>
> b) The proposed archive extension is .cb, 
> c) The proposed MIME type is application/vnd.cocoon.block (to be
>registered at IANA)
>
> / -> root of the block
> /BLOCK-INF/ -> container for the block manifests (this directory is
>shielded by Cocoon and will not be directly readable from the external,
>just like it happens for /WEB-INF/ for WARs)
> /BLOCK-INF/lib -> contains the libraries (.jar, .dll, .so)
> /BLOCK-INF/classes -> contains the classes (.class, in their right
>package location, as for WARs)
> /BLOCK-INF/block.xinfo -> XML file that contains the block informations
>along with component roles and configurations, sitemap/flowmap mounting,
>and external block dependencies.
> /** -> all of the remaining resources

<Ahem> just to get a picture. Do we speak here from Avalon Phoenix
blocks, or something homegrown?

Because when we speak of Phoenix, the assembly of the Application
would look different. (Paul, please correct if I'm wrong here!).

>  d) a URI-based protocol will allow polymorphic access to cocoon blocks
>and inter-block sharing of resources. The proposed syntax is
>
>  block(role):/path/file
>
>and 
>
>  block(role):component
>
>for example
>
>  block(skin):/stylesheet/document2html.xslt
>  block(calendar):date-generator
>
>NOTE: the above is compatile with the URI syntax as described in RFC
>http://www.ietf.org/rfc/rfc2396.txt.
>
>In case the block role is ambiguous, it will be used as a namespace
>prefix, as in
>
> <map:match ...>
>  <map:generate src="block(role):/path/file"
>xmlns:role="http://www.role.com"/>
>  <map:transform src="block(role):/path/file"
>xmlns:role="http://www.myrole.org"/>
> </map:match>
>
>if the block-based URI is used in non-namespaced syntax (for example, in
>the flowmap), an API-based solution will be provided.

BTW: Great idea...maybe Cocoon 3.0 huh ;) ?

  ~Gerhard

 
"Confucius say too much.
(Recent Chinese Proverb)"


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message