Re: [RT] Another step to blocks: Application container support

["Bradley S. Huffman" <hi...@cs.okstate.edu>]

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

Re: [RT] Another step to blocks: Application container support

[Carsten Ziegeler <cz...@apache.org>]

Bradley S. Huffman wrote:
> 
> I still trying to get acquainted with Cocoon so this may be a silly question,
> but why cann't anything come after a serializer?
> 
The answer is simple :) This is the way how the behaviour of the sitemap
has been defined years ago. So, also you can write something after a
serializer in the sitemap, it is *never* executed.

Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/