I see...I wonder what was johan (where he suggested using hybridurlcodingstrategy) and maurice refering to when he mentioned that it would be the same page instance is reused (and hence i assume the model with it too) given its a non-bookmarkable page
You have got a valid point, but its just that the particular use-case i am using this page for, can be considered as fetching the data from a non-oltp db so the data would ever change thats why.... Jonathan Locke wrote: > > > okay, so i think the answer to your question is no, you can't optimize > that. you should be using detachable models and an OTS db cache. > > what i don't understand is why you want to do this. if the user hits > refresh in their browser they are hoping to see updated data. why do you > want to turn that into a no-op? > > > mfs wrote: >> >> I have the condensed version of the code here, with some comments on the >> top of each class.. >> >> http://papernapkin.org/pastebin/view/788/ >> >> Waiting for follow up >> >> >> Jonathan Locke wrote: >>> >>> >>> you must be making some mistake (probably conceptual). can you create a >>> quickstart example of your problem and post it at some link where we can >>> see exactly what you're doing? >>> >>> >>> mfs wrote: >>>> >>>> Well actually before posting this up, i did try this i.e. mounted the >>>> page using hybridurlcodingstrategy (with the assumption that since the >>>> pageId is there in the url doing a refresh would load the already >>>> instantiated page against the id) but at that time i had the page as >>>> bookmarkable (i.e. had public default and param constructors), so after >>>> reading maurice's post, i made it a non-bookmarkable one (by making >>>> both the constructors as protected) but unfortunately it still doesnt >>>> work, doing a refresh i still see the updated model..to be precise i am >>>> using a DataView which is a IDataProvider and am using non-detachable >>>> models. >>>> >>>> Thanks for the follow up.. >>>> >>>> >>>> >>>> Johan Compagner wrote: >>>>> >>>>> HybridUrlEnoding >>>>> >>>>> On Sun, May 11, 2008 at 9:04 AM, mfs <[EMAIL PROTECTED]> wrote: >>>>> >>>>>> >>>>>> Guys, >>>>>> >>>>>> Firstly, Is that a right understanding that doing a browser-refresh >>>>>> of the >>>>>> page would result in a new instance of the page being created >>>>>> everytime and >>>>>> similarly a new model instance would be binded to the page. >>>>>> >>>>>> Is there a way one can use the same version of the page/model (which >>>>>> wicket >>>>>> kept in the session) when the page was rendered the first time.. >>>>>> >>>>>> I would want to avoid a hit to the database on refresh (since my >>>>>> model >>>>>> construction requires so) >>>>>> -- >>>>>> View this message in context: >>>>>> http://www.nabble.com/Load-serialized-%28or-in-session%29-page-model-on-refresh..-tp17170105p17170105.html >>>>>> Sent from the Wicket - User mailing list archive at Nabble.com. >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > > -- View this message in context: http://www.nabble.com/Load-serialized-%28or-in-session%29-page-model-on-refresh..-tp17170105p17181374.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
