cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <>
Subject RE: Fortress Migration Strategy
Date Thu, 16 Oct 2003 08:29:00 GMT
Leo Sutic wrote:
> > From: Carsten Ziegeler [] 
> > 
> >   So in this sax streaming we have a class called
> >   EnvironmentChanger that takes care that the current collection
> >   used is the correct one.
> >   So if the sub request sends an event to the main request,
> >   a pointer is set pointing to the collection of the main
> >   request. When this event is finished it is reset.
> OK... So, if I understand this right, then the entry-exit from these
> environment "bubbles" are method call and return, respectively? I.e.
> Pipeline stage A (a generator) has its own Environment, and when it
> calls startElement on stage B (in another request) then you switch
> Environment? And you switch back when the thread returns to A?
Yes, exactly.

> Could this not be realized via interceptors?
What do you mean by this?

Ususally A would stream directly to B, with the changer
A streams to the changer and this streams to B.


View raw message