On 11/29/05, Adam Hardy <[EMAIL PROTECTED]> wrote: > Michael Jouravlev on 29/11/05 16:54, wrote: > > Both Struts Dialogs example and DisplayTag library use session-scoped > > data to display in pages. > > I haven't checked out either the struts dialog pagination or the > displaytag, so I'm not sure how they deal with multiple browser windows, > but if you are keeping just one session-scoped dataset under one key, > then multiple windows will mix up their lists. Guess it depends how open > your requirements are.
Yes, that is true. This is the major limitation of having session-scoped form beans or other singleton-like objects. On the other hand, how often you saw a regular user, who used "Open in new window" browser action? Also, it is harder to open a new window with a pushbutton, than with a link ;-) I think that benefits of session-scoped data weigh more than drawbacks. Wicket guys don't think much about it, and just create new object in the session when you click on the link. Now they are working on limiting session size. Wicket allows to refer to a single model from several pages, which was recommended to me as a way to limit number of pages. But having several page instances and one model does not make much sense to me, the data is shared and can be corrupted. So, this is not much better than simple approach I use now. Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
