Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <492C251D.40501@apache.org>
Date: Tue, 25 Nov 2008 17:17:33 +0100
From: =?ISO-8859-1?Q?Reinhard_P=F6tz?= <reinhard@apache.org>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Where is Cocoon 3 going to?
References: <4925FD53.1020002@apache.org>
 <4925FFB0.8090503@tuffmail.com>	 <F8E386B54CE3E6408F3A32ABB9A7908A01537838@hai02.hippointern.lan>
	 <20081125000506.GB376@igg.indexgeo.com.au>	 <492BE41D.50904@tuffmail.com>
 <492C0AA5.4030209@apache.org>
 <cc159a4a0811250810i4b1739f9i2b4240092bed566d@mail.gmail.com>
In-Reply-To: <cc159a4a0811250810i4b1739f9i2b4240092bed566d@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Peter Hunsberger wrote:
> On Tue, Nov 25, 2008 at 8:24 AM, Reinhard P�tz <reinhard@apache.org> wrote:
>> Grzegorz Kossakowski wrote:
>>> Cocoon 3.0 started by Reinhard looked promising to me but now I
>>> realize that the main idea of its existence is to more or less
>>> rewrite C2.2 and add some RESTful features.
>> Yes, that's explained by the first paragraph of the Cocoon 3 website.
>>
>>> It's not my intention to criticize anyone but I really think it's not
>>> enough to make others excited and willing to contribute. At least it
>>> looks that way...
>> You probably have missed it but with Simone we actually have one very
>> active committer and I know that many other people are fond of the
>> Cocoon 3 pipeline module.
>> Currently the main problem is that most developers don't know that there
>> is such a simple thing as the Cocoon 3 pipeline library. I've already
>> started to provide documentation but haven't got very far yet. But be
>> assured that it has a very high priority on my opensource todo list.
>>
>>> Has anyone here thoughts on this topic or it's only me who has a
>>> problem?
>> When I started Cocoon 3 my main goal was to solve two problems: 1)
>> provide a plain and simple pipeline API that is easily usable from
>> within any Java environment 2) make Cocoon a simple platform for RESTful
>> services.
>> This made *me* excited about it and solves *my* problems. I haven't done
>> any market research about what would have excited others.
>>
>> Anyway, I don't think that it makes much sense to talk about what an
>> anonymous mass of people might want. So Grzegorz and all others reading
>> this, what would make *you* excited about Cocoon 3 so that *you* would
>> be willing to contribute?
>>
> 
> FWIW, we'll be taking a hard look at moving to Cocoon 3 vs. 2.2 as we
> look at migrating off of 2.1.  Our main requirement really is for XML
> and XSL pipelines and we don't use most of the existing Cocoon
> infrastructure, the big thing currently lacking is 3 that we really
> need is caching...

Could you elaborate on your caching requirements?

-- 
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                  reinhard@apache.org
________________________________________________________________________