cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bradley S. Huffman" <...@cs.okstate.edu>
Subject Re: [RT] Another step to blocks: Application container support
Date Fri, 11 Mar 2005 21:41:44 GMT
Carsten Ziegeler writes:

> Currently I see the need for two additional features:
> 
> a) "a request listener" - I want to be able to act on each request
> comming into my sitemap; and in addition I would like to do something
> when the request is finished which means *after* the serializer wrote
> the content into the stream. Now, doing something on each request *can*
> be done by using actions or some flow script; but actions can't be run
> after the serializer and it's a lot of overhead to use flow script for
> each and every request.

I still trying to get acquainted with Cocoon so this may be a silly question,
but why cann't anything come after a serializer?

Brad

Mime
View raw message