Hi Dave, I am afraid I disagree with you on this point. Even when validation fails, redirect after post does make sense. Although you're right that double submission is not a problem when validation fails. If you respond directly to a post, the post will get into the browser's history. This is a problem when the browser's back button is used. This would result in the ugly dialogue "Do you want to send formdata again..." popping up. This can only be avoided by never directly responding to a post-request.
Regards, nillehammer Dave Greggory schrieb: > While I highly agree the redirect-after-post pattern is a good practice. It > only makes sense in some situations. It makes sense to use it when you're > submitting a form and the form submission was successful (ie. Tapestry > "success" event fires). But if validation fails, Tapestry should not be using > a redirect to re-show the form with the validation errors. > > When validation fails, it should use the response for the same request for > re-showing the form, it should not be sending a 302. I wish there is a way to > disable redirects for validation failures only. > > > > ----- Original Message ---- > From: Robert Zeigler <robe...@scazdl.org> > To: Tapestry users <users@tapestry.apache.org> > 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 instance), but if you're > really concerned about it, there's a configuration option to turn it off. > > In org.apache.tapestry5.SymbolConstants: > > /** > * If set to true, then action requests will render a page markup > response immediately, rather than sending a > * redirect to render the response. > */ > public static final String SUPPRESS_REDIRECT_FROM_ACTION_REQUESTS = > "tapestry.suppress-redirect-from-action-requests"; > > > Cheers, > > Robert > > 11, 2009, at 3/1110:35 AM , rajesh sukumaran wrote: > >> 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 requests. Will this not affect the performance of Tapestry >> applications, especially under high load? Redirects will result in an >> additional HTTP hit on the server for every event request that is rendered >> by a different page. Will this not degrade the responsiveness of the web >> application as the load increase? >> >> I would like to know what everyone thinks about this? >> >> regards, >> Rajesh >> >> >> >> >> Add more friends to your messenger and enjoy! Go to >> http://messenger.yahoo.com/invite/ >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- http://www.winfonet.eu --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
