if you dont want redirect call: setRedirect(false) johan
On Nov 22, 2007 6:57 PM, Stefan Simik <[EMAIL PROTECTED]> wrote: > > Hello Wicketeers, > > I prepare report about rendering strategies (for studying community in our > company) and conceptually I understand all the things, but I have one > question, that I cannot answer. > > The default rendering strategy is RENDER_TO_BUFFER, because it solves both > problems of > two previous strategies: > 1. no double submit problem > 2. no potential problems with double attaching/detaching models > > But in my mind, I have problem: > When some aplication has 90% of pages, that are only for viewing, and 10% > of > pages, that submit form, > then I see, that for 90% of the view pages is the redirect not useful. For > these 90% pages would be sufficient only ONE_PASS_RENDER strategy, because > there is no need for redirect from my point of view. > Only 10% of pages takes advantage from redirecting. Does'nt it make 90% > of > needless redirects ? > > Is it not possible tu use REDIRECT_TO_BUFFER strategy only for POST > request, > and for all GET request > respond with ONE_PASS_RENDER ? But in WicketFilter all POST's call GET, so > I > think it's not possible. > > Is there anything I forgot to think about ? > > Thank you for you answer > > Stefan Simik > > > > > -- > View this message in context: > http://www.nabble.com/Rendering-strategies-question-tf4857740.html#a13900891 > Sent from the Wicket - User mailing list archive at > Nabble.com<http://nabble.com/> > . > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
