Hi, the other strategies always create new page instance. The difference with hybridurlcodingstrategy is that it attempts to reuse existing page instance (when pageid in session matches the class specified by mount point).
-Matej On Jan 29, 2008 11:36 PM, mfs <[EMAIL PROTECTED]> wrote: > > Guys, > > I believe its just the "HybridURLCodingStrategy" and its subclasses > (IndexHUCS) which encodes the mount point, page parameters and page > instance > information into the URL whereas others strategies DO have the mount-point > & > page-param in them (encoded in a different way) BUT the page-instance info > (i.e. page-id/version) is not contained in the URL. I wonder why is this > page-info not required by other strategies, wouldnt it be need to locate > the > older pages AND IF NOT how does it work for them...cant it work in a > similar > way for HUCS where we dont have those numbers in the url... > > Thanks in advance > > > > > -- > View this message in context: > http://www.nabble.com/HybridURLCodingStrategies-vs-others-tp15171137p15171137.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] > > -- Resizable and reorderable grid components. http://www.inmethod.com
