Well that was just hypothetically speaking..what i meant was it would have loads of data loaded in it..so it was that scenario where i was wondering that we shouldnt store the state of each page. Yes as you pointed out using detachable models can certainly be one to way to go..but at the same time since i am sort of presenting my company with all the features, i want to be prepared with answers and would want to know as much as i can..
So with what i understand the page serialization can be disabled by providing a dummy page-store but the storage of pages in the pageMap and hence in the current active session is something which is implicit and not something we can avoid.. Eelco Hillenius wrote: > >> Now there would be certain use-cases/pages in our application which would >> have alot of data in it (lets say in mbs), and in that scenario storing >> the >> entire model-data/components would probably bring in too much of a load >> on >> the system (in my opinion...given high volume of users..) so with that >> may >> be we would not want to store the pages in pageMap at all (which in turn >> is >> stored in the session). > > But I hope you're not storing MBs of data in your pages?! Users will > also get pages served that are MBs large? Note that you don't have to > keep anything in memory if you work with detachable models. > > Eelco > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Disabling-serialization-storage-of-pages-in-session--tf4768006.html#a13653854 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
