StrutsCatalogInputOutputSeparation continued / PRG

["Benedict, Paul C" <pa...@merck.com>]

Michael,

I want to continue this discussion because I think it has merit.

I've used the PRG pattern for over a year since I first came across your
article on TheServerSide.com. It works well in most cases, but I don't use
it 100% of the time because of certain limitations. It just happened that
your positing to the Struts Wiki brought up this subject again, and, to me,
and it's worth revisiting.

I only implement PRG on hard operations (such as saving or deleting, as
opposed to viewing) that succeed. Redirecting after a successful operation
that concretely alters data is critical to prevent the POSTDATA situation.
However, I do *not* implement PRG on loading an item for viewing/editing or
a failed save/delete. I deviate from your recommendation because (1) I want
to keep automatic Struts validation and (2) I do not want to put errors and
messages in the session. 

Can you give me some strong arguments to why I should yield from my
preference? I want to see the benefit.

As a general rule, my forms are request scope because I do not want to tie a
user's view to their session. For instance, I've seen clients who CTRL+N in
Internet Explorer and surf around a web application in two separate views --
what makes this special is that IE allows different views (windows) to be
under the same session!! By altering the app in one window, the other window
could be adversely affected on its next request. So, for instance, could
your recommendation allow editing of two simultaneous WhateverForm items
within the same session? This is an important requirement that I cannot
lose.

Thanks,
Paul






------------------------------------------------------------------------------
Notice:  This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or its affiliates (which may be known outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD and in Japan, as Banyu) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message.  If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system.
------------------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org