I have a few question regarding the wicket usage. we are trying to Implement wicket as our next MVC framework, Can please someone answer the questions below
- about session support - wicket stores the render state of most renderer's in session for different users of the systems. This means large/very large sessions that need to be supported, means memory crunch, performance degradation and implementing the failover at production level really hard. - Also it looks like wicket requires code changes when more pages are added and each page needs to have separate handler and it can not be done in configuration file. This may become an issue when number of pages increase in future. Dummy -- View this message in context: http://www.nabble.com/Wicket-Session-Management--tf4721575.html#a13498748 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
