> 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..
But it is really premature optimization to worry about this now. If you are worried about this, the best thing you can do is write an actual page (or a couple) and load test it and see how it behaves. Much better than wild guessing what you think might happen :-) > 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.. Only the current page yes. Unless you work with stateless pages, which don't get stored it the first place. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
