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
