> 1) You mentioned tweaking the number of history items kept in the > session as something to make sure to pay attention to. I understand > wicket keeps a history of the component tree in the session on a > render by render basis? Do you know of a good source where I can learn > more about this mechanism?
If you're using 2.0, this is actually not really an issue when you use the defaults. By default in Wicket 2.0, the session will only hold the current page instance, and older instances/ versions are written to a temp dir. Those older instances are only needed when the user presses the back button, which should only be a fraction of the actions performed in a web app. > 2) Is there a ballpark estimate for Wicket 2.0 (3 months, 6 months, 1 year) ? The rough estimate is that we want the API fixed (other devs, still reading with me?) by the end of this month; we need that because we're getting nearer to finishing Wicket In Action, and also because we have been working on 2.0 for over half a year now and we just need to fix it some time. When the API is fixed, we can churn out betas and it'll be a few months until all the nitty gritty details are settled (though so far, there have not been that many urgent problems with 2.0). Eelco ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
