Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Date: Thu, 29 Mar 2001 12:29:13 -0500 (EST)
From: Donald Ball <balld@webslingerZ.com>
To: <cocoon-dev@xml.apache.org>
Subject: Re: strange resons not going beta (was Re: C2: trouble getting
 streaming to work as expected)
In-Reply-To: <985875694.3ac344ef01eb2@mail.otego.com>
Message-ID: <Pine.LNX.4.30.0103291225160.7233-100000@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 29 Mar 2001, Giacomo Pati wrote:

> This is the first time I've read that the missing features (aggregation and
> caching) are strange reasons not going beta/production with Cocoon 2. Let me
> check this out. Who else finds this is strange.
>
> 1. Can you imagine that C1 users today will switch to C2 without a cache?
>
>    The fact is that C2 cannot compete with C1 (with cache enabled)
>    for static content delivery. This might lead to the situation
>    that we will support and maintain two versions at the same time.
>    C1 for faster static content delivery and C2 for dynamic publishing.

i dunno. c2 is pretty fast in and of itself.

> 2. Is content aggregation a feature we need to go beta/production?
>
> I've only follow Stefano reasoning that those features are needed to
> go beta/production. But you all can convice me to change my mind :) If
> most of you find these features are not needed for going
> beta/production we should ask on the user list what those people think
> about. I know C2 is very stable on what is implemented so far from
> projects I've realized with it (only dynamic systems which doesn't
> need caching). We all know that content aggregation will be a very
> cool feature to cut down your pages into smaller pieces collected from
> different sources almost like browser use HTML frames but with a total
> different granularity (frame technology on the server side). And thus
> having a cache can boost performance of such aggregation tremendously.
>
> So, what are you oppinions on this?

content aggregation would be very helpful before going beta. in my mind,
beta code is supposed to be largely stable in two ways - it shouldn't
crash all the time for inexplicable reasons, and the API and configuration
files' formats shouldn't be changing wildly. if we can add content
aggregation to the sitemap, i think we'll be at a point at which we could
get a beta release out there for people to play with. and really, how hard
can content aggregation really be compared with the very difficult
problems already solved? i'd try to do it myself, but i'm swamped helping
develop an in-house CMP using EJB's.

- donald


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