cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <sylvain.wal...@anyware-tech.com>
Subject Re: Release early? (was: Roadmap Executive Plan)
Date Mon, 11 Mar 2002 13:09:42 GMT
Carsten Ziegeler wrote:

>Hmm, "release early" what does it mean?
>I think we should release a new version before lunch. Is that
>early enough?
>
>Ok, odd joke, let's get serious now:
>
>The problem with Cocoon and release early is the wast amount of
>changes that occur between versions. But I really would like
>to make a 2.0.2 asap.
>As I couldn't follow all the changes and discussions in the
>last two weeks, can someone summarize this please? Are the changes.xml
>up-to-date?
>
>I have at least two topics I would like to address:
>
>a) Sitemap components in the cocoon.xconf.
>Now, personally I don't like this - but that's my own opinion about this.
>If you want to edit the sitemap, you not only have to look at the sitemap
>but also at the cocoon.xconf. This makes handling the sitemap even more
>complicated.
>I know a lot of people complaining about the complexity of Cocoon and
>the many places of configuration. By this splitting of component definition
>it gets even harder for beginners.
>So I would like to have all these definitions back in the sitemap.
>What is the benefit of having them in the cocoon.xconf?
>
The benefit is reduced length of the <map:components> section in the 
sitemap, which is both tedious to copy/paste in every sitemap and really 
frightening for some beginners, and provide some sitemap components to 
other components that could use them (thinking mainly about the xml 
serializer).

About frightened users, what about reversing the order of sections in 
the sitemap : start with pipelines, which describe the contract with the 
external world, then resources, view, actions and lastly components ?

>b) the sunRise and sunSpot components
>What is the feeling of the community to move them out of the scratchpad
>into the main trunk? I'm - of course :) - +1 on moving them.
>
Before moving sun* to the main trunk, we should discuss how it could be 
better integrated into Cocoon. For now, it's in Cocoon's CVS (thanks 
again for this donation), but is built 'on top' of it, while some of its 
components are of general purpose and could be moved in existing Cocoon 
packages where they could gain more exposure and thus a wider use.

A question about sunRise : is it possible to use standard HTTP 
authentication and authorization ? AFAICS, it seems to be very tied to 
form-based and application-managed authentication.

<snip/>

Sylvain

-- 
Sylvain Wallez
  Anyware Technologies                  Apache Cocoon
  http://www.anyware-tech.com           mailto:sylvain@apache.org




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


Mime
View raw message