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,

Are there any other knows issues with 'ONE_PASS_RENDER' render strategy?

Also what is the use of the below API?

Does it make any difference to the render strategy? I guess it makes some
difference to 'REDIRECT_TO_BUFFER'. 


View this message in context: 
Sent from the Users forum mailing list archive at Nabble.com.

To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to