Storing these in the session makes them persist across calls, whereas
storing them in as request objects makes them 'local' to that particular
request (ie non-persistant).
Regards,
Anthony Aldridge
Lead Application developer
Managed Intranet Hosting
CSC
JPMorganChase
Personal GDP: 325-8338
MIH Hotline: 876-1300
terracare <[EMAIL PROTECTED]> on 06/12/2001 13:52:28
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: Request attributes?
> Temporary storage (and passing of vars down the chain) is precisely what
I
> use the attribs for. Here's a bit of code for sending an id to another
> object via the Request object:
>
> req.setAttribute("jbxsp-id",instanceId);
> instance.setReq(req);
Up to now I have used sessions to store objects needed further down the
processing chain. I may be mistaken, but this approach seems to be a lot
more efficient, assuming I don't need the object outside of the chain... Is
this correct?
Thanks.
Diana
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
