Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Date: Thu, 27 Mar 2008 18:40:28 +1100
From: David Crossley <crossley@apache.org>
To: dev@cocoon.apache.org
Subject: Re: Layered software designs
Message-ID: <20080327074028.GD7496@igg.indexgeo.com.au>
References: <47E7F20D.3020308@tuffmail.com> <47E8A7CE.6040508@apache.org>
 <47E9061C.5030105@tuffmail.com> <47E911D9.9040503@apache.org>
 <47E9B1CA.6050202@gmx.de> <47E9FC91.3080004@apache.org>
 <47EA1B66.5040907@apache.org> <47EA4C3D.9070802@apache.org>
 <20080327065746.GB7496@igg.indexgeo.com.au> <47EB4A51.2000708@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <47EB4A51.2000708@apache.org>
User-Agent: Mutt/1.4.2.2i

Reinhard Poetz wrote:
> David Crossley wrote:
> >Reinhard Poetz wrote:
> >>A simple scenario could be:
> >>
> >>  Pipeline API  +  java.net.URL   +  XML-SAX components
> >>
> >>A more advanced scenario could consist of
> >>
> >>  Pipeline API  +  Sourceresolve  +  XML-SAX components  +  Sitemap Engine
> >
> >Is "sourceresolve" where the Apache XML Commons Resolver
> >is hooked up?
> 
> no, I was talking about the Excalibur Sourceresolve component.

Yes, i know. However that might involve the Catalog Entity Resolver too.
This configuration used to be done in Cocoon, then we
moved it to Excalibur so that it would be more widely used.

> >I would be concerned if our base offering enabled
> >mis-use of net resources, e.g. processing an xml file
> >which declares a DTD, causes an extra network trip if
> >we don't have the xml entity resolver.
> 
> Resolving XML entities is important and we will definitly offer solutions 
> for it in the future too.
> 
> Corona, Steven's and my proposal of a Cocoon reimplementation, is about 
> doing things differently so that Cocoon becomes easily embeddable and 
> reuseable from within as many environments as possible. We think that a 
> "layered design" is the key to achive this goal. When you put all layers 
> together, the result (= a web application framework) should be nearly[1] as 
> powerful as that what we have today.
> 
> For that purpose Steven and I have also started to reimplement existing 
> concepts instead of doing everything from the scratch. First, we believe 
> that many of the existing concepts are good as they are and second, this 
> makes it easier for others to chime in because if you see Corona as a black 
> box, it should (more or less) provide the same results as 2.x.
> 
> HTH

Yes it does.

-David

> [1] The only exceptions are things that we want to remove, e.g. sub 
> sitemaps etc. -> see the Micro-Cocoon discussion: 
> http://marc.info/?l=xml-cocoon-dev&m=119903256406947&w=2
> 
> -- 
> Reinhard P?tz                            Managing Director, {Indoqa} GmbH
>                           http://www.indoqa.com/en/people/reinhard.poetz/
> 
> Member of the Apache Software Foundation
> Apache Cocoon Committer, PMC member, PMC Chair        reinhard@apache.org
> _________________________________________________________________________