Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Message-ID: <38A96814.A098F9A0@apache.org>
Date: Tue, 15 Feb 2000 15:52:04 +0100
From: Stefano Mazzocchi <stefano@apache.org>
Organization: Apache Software Foundation
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: Variations on a theme by Cocoon
References: <38A88961.AD92FAB@apache.org> <38A8D5B5.82293A33@netmanage.co.il>
 <38A8ED5D.379AC8F3@localbar.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Niclas Hedhman wrote:
> 
> Zvi Avraham wrote:
> 
> >
> > Sounds OK to me, but I wandering if possible to "linearize" entire path of
> > producer -> filter -> serializer
> > or
> > producer -> filter1 -> filter2 -> ... -> filterN -> serializer
> > compile all this into one .class file (Servlet) ?
> >
> > Then you even don't need Cocoon in runtime, only in design time (compile
> > time? :)
> 
> This is not a clear cut case.
> 
> First of all, this is already possible. Generate the Site content into static
> html files and have them served by the web server. Won't get faster than that
> in runtime.
> 
> But, that is not the issue.
> 
> If you have the pipeline above, one must evaluate the "cost of validation" CoV
> and "cost of regeneration" CoR versus "frequencies of change" FoC (dynamic
> content for instance) versus "Cost of Transport" CoT.
> If you are using smaller stages, the FoC will drop, CoV will be roughly the
> same and CoR will be reduced. CoT will be increased due to more transporting
> stages, but possibly a lot lower with SAX.
> One should possibly also introduce "Regeneration Latency", which will increase,
> possibly exceeding "Maximum Allowed Latency".
> 
> This is a pretty complex formula, but I think it would be safe to say there are
> no clear and simple answers. It all depends on the scenario of static versus
> dynamic and semi-dynamic content, request frequency, content volume and other
> factors.

I totally agree.

The "producer production" case is needed when the frequency of change is
_very_ low compared to request frequency (I'm talking about production
environments, not developing evironments which simply have different
requirements).

Anyway this is the same old tune as for compiled servlet pages and
embraces all web technologies that are able to compile scripted pages.

So, while it is possible, in theory, to "linearize" a pipe into big
servlets, I see this done _only_ in very special cases... and, BTW, a
wiser use of Changeable/Modificable would do a much better performance
increase.

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------
 Come to the first official Apache Software Foundation Conference!  
------------------------- http://ApacheCon.Com ---------------------