On 11/30/05, Adam Hardy <[EMAIL PROTECTED]> wrote:
> From: Michael Jouravlev
> To: Struts Users Mailing List
> Sent: Wednesday, November 30, 2005 12:41 AM
> >   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.
>
> Guess I'm not your regular user then. I use the middle button on my
> mouse to open new tabs in firefox all the time. Admittedly there are not
> many webapps where I would do it which I can think of as examples, but I
> do this in e.g. mailing list archives all the time.

I do the same, but you and me are not regular end users, are we? ;) I
think of going on edmunds.com and right-clicking on the image link
only to get the same page in another window. These guys show images in
a popup window using Javascript, and suppose that users always
left-click. This arrogance infuriates me, but considering that such a
huge site implemented this design, and they are pretty successful, I
conclude that most users use left button only. Also, there are Mac
users, too ;)

Your example works for me, because archive lists are not updated, so
who cares if you open ten windows with the same list? Oh, right,
paging. This can be screwed up. So, a page number should be a request
parameter, not a problem :)

Have you tried SelectAction, which can be called now from any action
class to dispatch a request? Its usage does not require from you to
use any other features of the library. All you have to do is to send
proper parameter identifying the event, that is all.

Michael.

--
Struts Dialogs, code-behind for Struts
http://struts.sourceforge.net/strutsdialogs

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to