On 10/10/06, Vadim Gritsenko <[EMAIL PROTECTED]> wrote:
Peter Hunsberger wrote:
> On 10/9/06, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
>
>> > But just adding all this stuff to request attributes is not that
>> > easy as
>> > unfortunately sub request are sharing the attributes with the main
>> > request. So whenever you use the cocoon protocol the main request and
>> > the sub request use the same set of attributes.
Sub request by definition is the separate Request object with own set of
attributes (potentially with ability to access parent or global request
attributes - via special convention, may be?). Once sub request is completed,
all sub request attributes shall be discarded, leaving environment only with
parent attributes. Does it make sense?
It's the bit about "potentially with ability to access parent or
global request" that seems to be the issue really isn't it? I can't
see how this would be optional?
--
Peter Hunsberger
