> 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.
And then I wrote:
> 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. [...]
On rereading this later in the day, I realize it comes off a bit
acerbic. That was not my intent, and I apologize if I offended you.
Perhaps it was just fatigue (or yet-another-meeting-with-the-businessfolk
syndrome).
I'm finding this quite frustrating, both because this seems like
it should be such a straightforward thing to do, and because most
(all?) of the replies I've seen are either "Set the headers to not
cache" (which I did...) or "why would you do that?".
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
