apestry 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?
>
>
It depends on the setup of your wizard, if it a single page iterating
over components or a series of tapestry pages following each other - but
either way you prevent such problems by persisting flow information in
the client, not as cookies but on a page - based in URLs.
You should always keep
TECTED]>
> >Reply-To: "Tapestry users"
> >To: Tapestry users
> >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
> >bette
;
> >
> >
> > --
> > Peter Beshai
> >
> > Pure Mathematics Student
> > University of Waterloo
> >
> >
> >
> >
> >
> > >From: Robert Breidecker <[EMAIL PROTECTED]>
> > >Reply-To: "Tapestry
t;
>Reply-To: "Tapestry users"
>To: Tapestry users
>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 req
t;
Reply-To: "Tapestry users"
To: Tapestry users
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 li
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
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
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 identificat
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 oth
10 matches
Mail list logo
