What about making this *not* the default, but - ofcourse - still support it the way it is?
Btw, when I was new with Wicket, setRedirect puzzled me; it was not immediately clear what would happen when I called that. How about 'setRenderAsRedirect' or something similar?
Eelco
Christopher Turner wrote:
The main drawback of option 2 is that it doesn't work in a round-robin clustered environment when the 'logical' request spans more than one physical request and physical requests are handled by different servers in the cluster.
I don't think that this is necessarily a problem provided that:
a) We make it very clear that the behaviour in a clustered environment is different than a non-clustered environment AND
b) The clustered application developer has enough hooks into the 'logical' request such that they can pull down objects (such as the hibernate session) at the end of one physical request and recreate them at the start of the next physical request.
Regards, Chris
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
