Henry J. Cobb ([EMAIL PROTECTED]) writes:
> The best way to "prevent" reposting is to retain the answer to the question.
>
> The user wishes to make exactly the same booking for the same nights at
> the same hotel with the same guests? Well, that's OK, I already know the
> results of all that, what happened with his credit card charge and even
> what his transaction number is. I don't need to bother the backend at all
> to simply redisplay the requested information.
>
> It's stuff like that that teaches one to separate process from display.
I'm not sure if you're replying to my post (in the "BACK-ing into
trouble" thread) or not. If you are, the above is irrelevant. When
somebody comes to me with a coding question, the first thing out of my
mouth is usually "Are you trying to solve the right problem? What are
you trying to accomplish?"
However, in this case, saving the results of the post is
irrelevant. The key issue is that the post-generated page contains
sensitive information, submitted by the user, and I don't want the
browser to keep the information around and repost it. I could
institute some kludges to keep the repost from going through on my
end, but I still don't want it to occur at all.
Steven J. Owens
[EMAIL PROTECTED]
[EMAIL PROTECTED]
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
