Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <3F8EB120.2090806@apache.org>
Date: Thu, 16 Oct 2003 16:54:24 +0200
From: Stephen McConnell <mcconnell@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Fortress Migration Strategy
References: <000d01c393be$01da5120$0801a8c0@lagrange>
In-Reply-To: <000d01c393be$01da5120$0801a8c0@lagrange>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Leo Sutic wrote:

>>From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de] 
>>
>>  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?
>
>Could this not be realized via interceptors?
>  
>

I'm thinking exactly the same thing.

Steve.

>/LS
>
>
>  
>

-- 

Stephen J. McConnell
mailto:mcconnell@apache.org