On 11/1/07, mfs <[EMAIL PROTECTED]> wrote: > > PageMap stores a single instance of a particular page ? OR could it have > multiple instances of the same page (browsed by user at different instances > against 2 different use-case lets say),
yes, it can have multiple instances of the same page-class > and if there could be muliple > instances of the same page, its just the page being viewed which is in the > PageMap (in session) > and the rest are all serialized on the disk, database etc... in 1.2.x they would all be stored in session, at least the last X instances. in 1.3 only the current page is in session (last viewed), the rest are swapped to disk. > ARE they all > rendered instances or the components and models are stored seperately...? they are not rendered instances, they are the page object with its component graph, stored in the detached state (detach() is called on page and all its children before serialization) > i am just familiarizing myself with the concept, i mean wouldnt we want to > have latest data against each page displayed every time, why version them > then ? is it there to handle the back button problem.. yes, versioning is done to support the back button, so an instance of the page can be retrieved in the "correct" state. -igor > > ALOT of questions at teh same time..just want to clarify the concept/idea so > if someone could be kind enough to shed some light ? > > Farhan. > -- > View this message in context: > http://www.nabble.com/pageMap-question---tf4735205.html#a13541168 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
