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)
Mime-Version: 1.0 (Apple Message framework v753)
In-Reply-To: <1F3E1E08-5C81-459E-9D03-0F233A9F04B1@reverycodes.com>
References: <4777C8C7.6060807@apache.org> <47D94AE8.7010900@apache.org>
 <1F3E1E08-5C81-459E-9D03-0F233A9F04B1@reverycodes.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <D82433CD-2938-42EF-9BC7-FA3379B9FC21@apache.org>
Content-Transfer-Encoding: 7bit
From: Torsten Curdt <tcurdt@apache.org>
Subject: Re: Micro-Cocoon ... Corona
Date: Thu, 13 Mar 2008 18:22:45 +0100
To: dev@cocoon.apache.org


On 13.03.2008, at 18:11, Vadim Gritsenko wrote:

> On Mar 13, 2008, at 11:40 AM, Reinhard Poetz wrote:
>
>> . a pipeline API (that isn't limited to XML pipelines but would also
>>   support connecting of any types of pipes)
>> . the pipeline API and the sitemap interpreter are useable from  
>> within
>>   *plain Java code* (-> no dependency on the Servlet API) --> if  
>> it is used
>>   outside of a web container, the user has to make sure that there  
>> is no
>>   component that uses the servlet API
>
> Speaking of which, I had intention to make a clear separation  
> between pipeline assembly stage - which is currently done by tree  
> processor - and pipeline execution stage - which is currently  
> sometimes is done from within tree processor itself, in case of  
> 'external pipelines', or out of tree processor for 'internal  
> pipelines'. I have done a prototype work - and had it working after  
> ~ 1 day effort.

When we had the whole 'cocoon is dead - let's rewrite it' discussion  
that was exactly one of the thing I was thinking of. To some extend  
the sitemap should be just a factory creating pipelines. The  
pipelines should be a completely separate stand alone API that is  
just used by the sitemap.

cheers
--
Torsten