cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Santiago Gala <>
Subject Re: strange resons not going beta (was Re: C2: trouble getting streaming to work as expected)
Date Thu, 29 Mar 2001 22:00:03 GMT
Berin Loritsch wrote:

> Giacomo Pati wrote:
>> Quoting Berin Loritsch <>:
>>> No that isn't.  Cocoon 2 is still (for some strange reason) considered
>>> Alpha software, so there are no direct downloads.
>> 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.
> Regarding Cache on C2.  Cocoon 2 is fast enough on my test systems and
> scalable enough on my systems that cache isn't critical.  We are talking
> blazing.  Cocoon 1 needs cache to even be useful--this is simple a state
> of DOM vs. SAX architectures and the speed of the libraries we are using.
> Cocoon 1 has discrete produce/process/format stages, while Cocoon 2 (due
> to the event based SAX model) does generate/transform/serialize in each
> event.  The stages are performed in effect simultaneously.

I agree, except for some SVG examples, for instance the svg-welcome. A 
cache would be great to have some kinds of processing, like svg or pdf.

I would sell very well an automated generation of graphic navigation 
bars, for instance, but that calls for a cache, obviously.

To unsubscribe, e-mail:
For additional commands, email:

View raw message