cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Homeijer <>
Subject RE: [C2]: Status report on caching - update
Date Thu, 12 Apr 2001 07:44:35 GMT
We have built a large dynamic web catalog in Cocoon 1. We have built an XML
framework with EJB and the XMLObject interface to get data from different
sources into an XML page. This data comes from the catalogue, but also from
language tables (labels, etc.), menu tables, and personalisation tables.

We are looking into migration to Cocoon 2 for performance reasons and I
think we now have two options:
- Implementing XMLFragment to get data from EJB into the resulting XML. For
maximum performance some of the objects implementing this interface should
be cached, either by us or by a standard from the Cocoon framework.

- Using content aggregation. This would mean much more effort, because the
resulting XML will change (and the accompanying XSL files should change), as
I understood from some mails about this subject.

I hope this explains my question.

Michael Homeijer
(Once the site we built is live on the web, and our client allows us to
spread some news, I will be happy to show somebody the catalog we have
built, so we might get some feedback on it).

-----Original Message-----
From: Carsten Ziegeler
Sent: 11-4-01 17:27
Subject: AW: [C2]: Status report on caching - update

> Von: Michael Homeijer []
> Hi,
> I am new to caching and to C2, but does caching of objects that
> XMLFragment into this?
Could you please further explain what you exactly mean?

The caching is based in the pipeline concept of C2. This has in the
run nothing to do with the XMLFragment.


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

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

View raw message