Well, you can use @Persist("client") to store your page state. That way,
when the page submits its request, it's actually sending the state along
with the request. So, even if you Ctrl-N in IE (or Ctrl-T in Firefox), the
separate windows will be sending their state independently of one another.
Or, you could use a transaction token (a la Struts) to keep things in synch.
If one page submits a token that doesn't match what's stored in your session
(create an ASO to store the token), then you inform them that they're trying
to do something illegal (i.e. using the site from multiple windows at the
same time).
-----Original Message-----
From: Vincent [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 23, 2006 8:04 AM
To: Tapestry users
Subject: Re: session id
Sorry James , can you tell me more details, I don't quite understand
what do you mean.
On 2/23/06, James Carman <[EMAIL PROTECTED]> wrote:
> Use hidden form fields to control the state of your application.
>
> -----Original Message-----
> From: Vincent [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 23, 2006 6:34 AM
> To: Tapestry users
> Subject: session id
>
> I found out that if two windows have same session id ( use ctrl + n to
> create a new one), one window operate with affect the other ones , is
> there any thing I can do to prevent?
>
>
>
> ---------------------------------------------------------------------
> 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]
