There has been some mention of this, but I've never heard of the details. Is this something that's planned? I've been thinking about it, and it may not actually be that bad. All you'd have to do is serialize all the models under a page into a base64 string (or equivelent), then plunk them all back into a fresh component tree on the next request: pretty much how .NET and JSF do it. That would solve all the back-button issues, you could get a totally stateless webserver AND have the killer wicket component model. Anyway, just some thoughs. I'm going to play around with it and probably figure out that it's a lot more complicated then that in the process. :)
------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
