I believe the transaction tokens in Struts are used for this purpose. Please don't tell me you're planning on breaking the user's back button :-). That's just web design 101.

David






From: "Ian Brandt" <[EMAIL PROTECTED]>
Reply-To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
To: "Struts Users" <[EMAIL PROTECTED]>
Subject: Handling common client "misbehaviors" (back button issues, multiple form submits, etc.)
Date: Mon, 25 Nov 2002 14:44:50 -0500


Hello All,

I've been hunting around to see if I could find a package which
offered a standard way of handling the common request issues that web
apps sometimes have to handle (things like back button issues on
multi-page forms, request fudging by the user that for one reason or
another you want to disallow, etc.). I'm thinking something along the
lines of a "screenplay engine", where rules could be defined for page
flow that each request would be validated against. Having heard that
Struts provides a standard web-app framework I went searching through
the docs and FAQs to see if anything along those lines was provided,
but I'm not seeing that it is. Is that correct, and if so does anyone
know of are any other projects out there that aim to provide a
standard handling mechanism for these issues?

Thanks,

Ian


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to