Event driven publishing

[Tero Vaananen <te...@gmail.com>]

I am evaluating various technologies to achieve event driven web
publishing, and Cocoon is one of candidates.

Let me explain what I mean.

I have a message queue that recieves events in XML from various
sources (databases, other queues etc.). This queue would be hooked up
to a publishing system that publishes html pages based on the
information that arrives.

For example, I have a database, and a change is made to it. A trigger
is run in the DB and the changed data is posted to the queue as XML.
This information is located on various pages on the web site and I
have to trigger publishing for all those pages or page fragments that
will show this updated data.

Can Cocoon handle most of the publishing work? Are there mechanisms to
trigger a group of page updates based on the changes in the XML? What
needs to be added if there is no support out of the box?

Thanks.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: Event driven publishing

[Mark Lundquist <ml...@wrinkledog.com>]

Hi Terro,

On Dec 3, 2005, at 7:37 AM, Tero Vaananen wrote:

> Can Cocoon handle most of the publishing work?

Yes.

> Are there mechanisms to
> trigger a group of page updates based on the changes in the XML? What
> needs to be added if there is no support out of the box?

One way or another... can you describe this "XML message queue"?  Is 
that something you have now, or is it part of the architecture you 
conceive of to implement with whatever publishing technology you 
choose?

In the Cocoon world, I would think the most natural approach might be 
to think not of a triggered "push" update, but rather to let Cocoon 
pull from the XML source and cache the result.  In general there must 
be some way to tell Cocoon to invalidate its cache.  But this would my 
first instinct, though it's hard to tell w/o knowing more about what 
you need to do.  While it's certainly possible to use Cocoon to 
generate static HTML pages, it's really oriented more toward building 
everything dynamically but caching heavily, and that naturally leads 
you to more of a "pull" model.

best regards,
—ml—

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org