Mechanically, tokens work by setting a, well, token in the response to the user, then checking that token value in the action after they hit submit. If the token is different or doesn't exist then the user is forwarded to a place defined by the Struts developer, usually some sort of error page.
They're pretty trivial to implement. Googling for "struts tokens" should give you some more information. The important part is that the ability to prevent multiple form submissions and double updates is built into Struts. -= J > -----Original Message----- > From: Olivier Gourment [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 24, 2003 10:10 AM > To: Struts Users Mailing List > Subject: Re: double-click protection and double-update problem > > Tib, > > I am not using Struts yet, so I am not familiar with the Struts > specific classes and tags, and I would like to be able to recommend it > to my customer. > Could you elaborate a little or point me to useful links? In > particular, would you have an idea of how much development this > involves? > Thanks a lot, > > Olivier > > > --- Gemes Tibor <[EMAIL PROTECTED]> wrote: > > 2003. január 24. 14:16 dátummal Olivier Gourment ezt írtad: > > > Hi, > > > > > > I was not able to search the archive... > > > > > > > > 1) Double-Click Protection: when a user clicks twice on the same > > > button, the associated action is not executed twice... > > > 2) Double-Update Problem: when a user hits the Back button of his > > > browser, the refresh of the page does not execute the transaction > > > associated to the page twice. > > > > This is what the tokens are good for. > > > > Tib > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
