Re: The "Presentation" Layer

if you removes the back button (i.e. opening a new window) the back key
works as the back button.
additional to this you can try some as

<meta http-equiv="expires" content="0">
<meta http-equiv="pragma" content="no-cache">
<meta http-equiv="cache-control" content="no-cache">
<script>if
(history.forward(1)){location.replace(history.forward(1))}</script>

also you can add each page to an sub-transaction-id in cookie or hidden
field and don't permit input in your host program with a sub-trn lower than
the last.

Depending on the page or the application, we're permitting back or not,
sometimes back is good and facilitates the user job.

(good programming are not so easy)

Guillermo



On Mon, Jul 21, 2008 at 4:42 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

From: john e
Simply push the "back button" and you always get where you
were if you're lost.

The "back button" problem keeps surfacing year after year. And I don't
have an ideal solution. Except to acknowledge that it's incompatible with
database maintenance applications generally and rich user interfaces in
particular. And to explain that to users so they know what to expect, or
scale back the scope and capability and performance of the application to
cater to traditional Web surfers.

I have an interest in extending browsers to support transaction processing,
data entry, and database maintenance in production environments, where
personal productivity of end users is a heavily weighted priority. So in
that context, I suggest that the entry point of the application (the sign-on
screen) be launched in a Window that removes the back button. Even with the
back button problem, I see browsers as a better alternative than 5250 and
thick client user interfaces for database maintenance, generally.

Nathan.



--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.