It should be reasonably straightforward, but will require a decent, non-trivial amount of work/fiddling to implement really transparently. For me, it's, at the moment, just not worth the work. I've talked with James Carmen about this and I think, he wanted to do something like that, but don't know about the status of it.
Afaik, the most advance impl of this is what the JBoss/Seam guys did. You might want to have a look at that. Marcus > -----Original Message----- > From: Dirk Markert [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 30, 2006 7:20 AM > To: Tapestry users > Subject: Re: Multiple browser windows causing session issue > > Daniel, > > I googled for conversations/cookies but really did not find > any good links. > Do you have any links to the frameworks/conversation > technique you mentioned? > > Dirk > > 2006/11/29, Daniel Tabuenca <[EMAIL PROTECTED]>: > > > > This problem is typical with almost all frameworks. Most frameworks > > provide scoping data to the request or to the session. In order to > > handle thee kind of things better you need to have > intermediate scopes > > (called conversations in some frameworks). As you already noticed, > > turning off cookies uses the jsessionId to provide something like a > > conversation. However, you can implement this yourself too. For > > example I simply store a clientSide numeric Id which I call > > conversationId using the @Perist("client") annotation. I then store > > any data I need in the session using a Map with the > conversationId as > > the key. > > > > It'd be really nice for tapestry to provide some support > for this. The > > issues involved are I think only determining when to start/end a > > conversation and determining how long to keep/expire conversation > > data. > > > > > > > > > > > > On 11/29/06, Peter Beshai <[EMAIL PROTECTED]> wrote: > > > I'm not an expert on this stuff, but tapestry-flash may be of use > > > for > > the > > > previous/next page problem. > > > > > > http://howardlewisship.com/tapestry-javaforge/tapestry-flash/ > > > > > > > > > > > > > > > -- > > > Peter Beshai > > > > > > Pure Mathematics Student > > > University of Waterloo > > > > > > > > > > > > > > > > > > >From: Robert Breidecker <[EMAIL PROTECTED]> > > > >Reply-To: "Tapestry users" <users@tapestry.apache.org> > > > >To: Tapestry users <users@tapestry.apache.org> > > > >Subject: Re: Multiple browser windows causing session issue > > > >Date: Wed, 29 Nov 2006 12:33:51 -0800 (PST) > > > > > > > >Sorry, I guess I should have described my application > better. Two > > > >application windows are not required. > > > >However, the users would like to be able to open > multiple instances > > > >of the application at one time. In addition to the wizard, I was > > > >also having problem with my table component and its > previous/next > > > >page controls. > > > > > > > >Thanks for your reply. I was looking for a philosophical answer > > > >not just for my wizard, but for Tapestry applications in > general. > > > >Your reply was just that. > > > > > > > >--- Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > > > > > > > > > That's just how it works. With cookie based session > management > > > > > you are identified by a single cookie object that would be > > > > > available to the server regardless of which tab you > operated in > > > > > (this is a side effect of how they work with browser clients, > > > > > not the > > > > > sever) . With > > > > > jsessionid's the identification of someone is kept > strictly in > > > > > the urls, so it would make sense that what you wanted to do > > > > > would work with cookies disabled. > > > > > > > > > > Really though, I have to wonder if this is an actual > problem for > > > > > your application or not? I don't currently use any web > > > > > applications that require two browser windows to be open to > > > > > operate them. It would seem to be slightly counter-intuitive. > > > > > > > > > > On 11/29/06, Robert Breidecker <[EMAIL PROTECTED]> > > > > > wrote: > > > > > > I have a stateful Tapestry application which > > > > > includes > > > > > > a wizard that steps the user from one page to > > > > > another > > > > > > to collect input data. If I run my application in > > > > > two > > > > > > browser windows (or tabs) within the same browser session, > > > > > > each instance of my application steps on > > > > > the > > > > > > session variables in the the other instance. > > > > > > > > > > > > I noticed that the HTML for each application > > > > > contained > > > > > > the same jsessionid. I turned off cookies for my > application > > > > > > at the server level (Tomcat 5.5) and > > > > > then > > > > > > my application worked fine across two browser > > > > > windows. > > > > > > The URLs for both instances now include the > > > > > jsessionid > > > > > > in them and each jsessionid is different. > > > > > > > > > > > > Even though this works for me, is this really the > > > > > way > > > > > > to solve my problem? It seems like I must be > > > > > missing > > > > > > something in Tapestry that would handle this for > > > > > me, > > > > > > regardless if cookies are on or off. > > > > > > > > > > > > ~Rob Breidecker > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >_____________________________________________________________________ > > >_______________ > > > > > > Do you Yahoo!? > > > > > > Everyone is raving about the all-new Yahoo! Mail > > > > > beta. > > > > > > http://new.mail.yahoo.com > > > > > > > > > > > > > > > > > > > > > >------------------------------------------------------------------- > > > >-- > > > > > > To unsubscribe, e-mail: > > > > > [EMAIL PROTECTED] > > > > > > For additional commands, e-mail: > > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Jesse Kuhnert > > > > > Tapestry/Dojo/(and a dash of TestNG), team member/developer > > > > > > > > > > Open source based consulting work centered around > > > > > dojo/tapestry/tacos/hivemind. > > > > > http://blog.opencomponentry.com > > > > > > > > > > > > > > >------------------------------------------------------------------- > > > >-- > > > > > To unsubscribe, e-mail: > > > > > [EMAIL PROTECTED] > > > > > For additional commands, e-mail: > > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >_____________________________________________________________________ > > >_______________ > > > >Cheap talk? > > > >Check out Yahoo! Messenger's low PC-to-Phone call rates. > > > >http://voice.yahoo.com > > > > > > > > >------------------------------------------------------------------- > > > >-- To unsubscribe, e-mail: [EMAIL PROTECTED] > > > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > _________________________________________________________________ > > > Ne perdez pas de temps dans les files d'attente... > magasinez en ligne. > > > http://magasiner.sympatico.msn.ca > > > > > > > > > > -------------------------------------------------------------------- > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
