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.

        Henry J. Cobb   [EMAIL PROTECTED]          http://www.io.com/~hcobb
    Any sufficiently cool technology is indistinguishable from religion.

___________________________________________________________________________
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

Reply via email to