Yes, it is a good article. The author states that there is not yet a standard name for the scope that lies somewhere between a request and a session. In projects I've worked on, we've called that a "conversation."
So we have the following scopes: 1. Request (supported automatically) 2. Conversation (requires custom coding, e.g., using <x:saveState>) 3. Session (supported automatically) When using Struts, we built a framework that used an xml file to specify which actions used which beans, and then, upon execution of each request, our framework automatically deleted from the Session those beans that were not in the list for the action being invoked on that request. That was our "conversation." I'm anxious to try out <x:saveState> to see how it compares.... - Brendan -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Werner Punz Sent: Sunday, August 07, 2005 3:50 AM To: [email protected] Subject: Re: great article Btw... I have added links in the wiki to this absolutely great article. Werner ir. ing. Jan Dockx wrote: > I just found a GREAT article: > > <http://bugs.sakaiproject.org/confluence/pages/viewpage.action?pageId=49 81&showComments=true> > > > Thanks, UCB! > > Met vriendelijke groeten, > > Jan Dockx > > PeopleWare NV - Head Office > Cdt.Weynsstraat 85 > B-2660 Hoboken > Tel: +32 3 448.33.38 > Fax: +32 3 448.32.66 > > PeopleWare NV - Branch Office Geel > Kleinhoefstraat 5 > B-2440 Geel > Tel: +32 14 57.00.90 > Fax: +32 14 58.13.25 > _ > http://www.peopleware.be/ > http://www.mobileware.be/_
