Return-Path: 
 <cocoon-dev-return-28385-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 60664 invoked by uid 500); 17 Jun 2002 13:30:33 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 60570 invoked from network); 17 Jun 2002 13:30:32 -0000
Message-ID: <3D0DE4CA.8010509@anyware-tech.com>
Date: Mon, 17 Jun 2002 15:31:54 +0200
From: Sylvain Wallez <sylvain.wallez@anyware-tech.com>
Organization: Anyware Technologies
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.0rc2) Gecko/20020510
X-Accept-Language: fr, en
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: [PROPOSAL] "CachingPoint" Caching algorithm
References: 
 <Pine.LNX.4.43.0206131132520.10754-100000@fztig938.bank.dresdner.net>
 <3D0DD08D.2060201@anyware-tech.com>
 <20020617131020.GA10790@fztig938.bank.dresdner.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Michael Melhem wrote:

>Hi Sylvain,
>
>You will find my response to your comments below.
>
>On Mon, Jun 17, 2002 at 02:05:33PM +0200, Sylvain Wallez wrote:
>  
>
>>Michael Melhem wrote:
>>
>>    
>>
>>>Hi all,
>>>
>>>I have started work on new caching algoritm which is refered to as
>>>the "cachingPoint" alogrithm.
>>>      
>>>

<snip/>

>>That's a very interesting proposal, as it can speedup a lot 
>>multi-channel applications. However, you forgot to say how do you flag a 
>>sitemap component as being a cache point ?
>>Does it require a specific attribute (<map:generate src="foo.xml" 
>>cachepoint="true"/>) ?
>>Can it be related to view labels (<map:view name="foo" 
>>from-label="foolabel" cachepoint="true") ?
>>    
>>
>
>Actually, cachepoint points are determined automatically
>using the following algorithm:-
>
>In Pseudo code the basic idea is as follows:
>if current Node extends SimpleSelectorProcessingNode
>        and if context.getProcessingPipeline() != null
>                        context.getProcessingPipeline().informBranchPoint()
>
>In other words, as we build up the pipeline (via invoke()), 
>whenever we come across treeprocessor nodes which 
>extend SimpleSelectorProcessingNode, then that should indicate 
>to us that a CachingPoint should be flagged
>
>The cocoon-view case is treated separately. Here is an example from
>GenerateNode.java: 
>---------------------------------------------
>...
>if (this.views != null) {
>   //
>   //
>   // Inform the pipeline that we have a branch
>   // point
>   //
>   context.getProcessingPipeline().informBranchPoint();
>
>   String cocoonView = env.getView();
>   if (cocoonView != null) {
>...
>---------------------------------------------
>
>Note: informBranchPoint() simply does nothing if the selected 
>ProcessingPipeline does not support cachepoints
>  
>

That's a clever algorithm, but don't you fear it will create too many 
branch points (and so cache entries) that what is really required by the 
application ?

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