Hi, If you cannot use sticky sessions then you should not use REDIRECT_TO_BUFFER because the pre-rendered response is saved/buffered in the WebApplication on the current node and there is a (big) chance that the next request wont be processed by the same node.
You can use either ONE_PASS_RENDER or REDIRECT_TO_RENDER. I'm not aware of any issues with them. On Wed, Aug 22, 2012 at 7:25 AM, sudeivas <[email protected]> wrote: > Hello, > We are currently using Apache Wicket 1.5.6 in a clustered setup. We > have a custom built distributed session management based on memcached. Due > to infrastructure limitations, we cannot use sticky sessions. So I am > wondering whether 'ONE_PASS_RENDER' render strategy is the best solution for > my use case. > > Its mentioned below that this still has double submit problem, > http://wicket.apache.org/apidocs/1.4/org/apache/wicket/settings/IRequestCycleSettings.html > > Are there any other knows issues with 'ONE_PASS_RENDER' render strategy? > > Also what is the use of the below API? > getRequestCycleSettings().setBufferResponse(false); > > Does it make any difference to the render strategy? I guess it makes some > difference to 'REDIRECT_TO_BUFFER'. > > Thanks, > Suresh > > > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Which-RENDER-STRATEGY-is-best-for-clustered-setup-tp4651420.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
