that was interesting read... thanks
- Original Message
From: manuel aldana
To: Tapestry users
Sent: Wednesday, 11 March, 2009 11:28:53 PM
Subject: Re: Implication of client side redirect
read this, very interesting:
http://www.theserverside.com/tt/articles/article.tss?l
Thanks Robert. It is defenitly good to know that there is way to turn it off,
it keeps my options open.
- Original Message
From: Robert Zeigler
To: Tapestry users
Sent: Wednesday, 11 March, 2009 10:04:56 PM
Subject: Re: Implication of client side redirect
Hi Rajesh,
Tapestry
either.
Peter
- Original Message -
From: "Dave Greggory"
To: "Tapestry users"
Sent: Thursday, 12 March, 2009 02:23:47 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: Implication of client side redirect
Yeah, you're right about that.
Still
11, 2009 7:44:00 PM
Subject: Re: Implication of client side redirect
Hi Dave,
your message made me doubt and I immediately tried that out (on IE 6 and
FF 2). I was not able to reproduce, what you were implying. So I still
think that redirect after post solves the problem.
hat problem because if you hit
> Back button twice, you still get the same problem.
>
>
>
> - Original Message
> From: nillehammer
> To: Tapestry users
> Sent: Wednesday, March 11, 2009 7:15:38 PM
> Subject: Re: Implication of client side redirect
&g
Em Wed, 11 Mar 2009 20:31:30 -0300, Dave Greggory
escreveu:
Redirect-after-post does not really solve that problem because if you
hit Back button twice, you still get the same problem.
I disagree. You just have this problem when you submitted a form and
returned a page in the same reques
Redirect-after-post does not really solve that problem because if you hit Back
button twice, you still get the same problem.
- Original Message
From: nillehammer
To: Tapestry users
Sent: Wednesday, March 11, 2009 7:15:38 PM
Subject: Re: Implication of client side redirect
Hi Dave
ailures only.
>
>
>
> - Original Message
> From: Robert Zeigler
> To: Tapestry users
> Sent: Wednesday, March 11, 2009 12:34:56 PM
> Subject: Re: Implication of client side redirect
>
> Hi Rajesh,
>
> Tapestry follows the "redirect after post
How does the redirect-after-post mechanism affect a servlet based or portlet
based Tapestry system?
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.
rs
> Sent: Wednesday, March 11, 2009 12:34:56 PM
> Subject: Re: Implication of client side redirect
>
> Hi Rajesh,
>
> Tapestry follows the "redirect after post" principle. This has a lot of
> "pros" (avoiding double submission of forms, for inst
riginal Message
From: Robert Zeigler
To: Tapestry users
Sent: Wednesday, March 11, 2009 12:34:56 PM
Subject: Re: Implication of client side redirect
Hi Rajesh,
Tapestry follows the "redirect after post" principle. This has a lot of "pros"
(avoiding double submission of
read this, very interesting:
http://www.theserverside.com/tt/articles/article.tss?l=RedirectAfterPost
rajesh sukumaran schrieb:
Hi,
I am evaluating Tapestry 5.1 to see if I can use it in one of my new projects.
I see that Tapestry uses client side redirects to handle response for event
reques
Hi Rajesh,
Tapestry follows the "redirect after post" principle. This has a lot
of "pros" (avoiding double submission of forms, for instance), but if
you're really concerned about it, there's a configuration option to
turn it off.
In org.apache.tapestry5.SymbolConstants:
/**
*
13 matches
Mail list logo
