Thanks, > I guess you might as well get ready for some complaints :
> - Not so good Spring integration Why? Igor and a couple of others build some pretty decent Spring support now? It's all in HEAD, and there has to be a proper build for it made, but I think we now have Spring integration that most people are happy with. > - Heavy session usage (Specially from those MVC critics) Yeah, we know people will use that. As you can read in other mails/ comments I do not always agree that's a bad thing. If you do you calculations properly, it's really a bunch of pros and cons instead of just a simplified 'using the session is bad'. Furthermore, we abstracted the session, so it is ready for alternative strategies too. Anyway, it's also what I am working on for 1.2. I am seriously out of time - whish I had more time for the refactorings - but one of my ultimate aims is to make zero-server state apps with Wicket possible too. Don't know whether I'll succeed in that, but you'll surely end up with a lot of hooks to optimize session usuage. Eelco ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
