Re: Where to send !isTokenValid(request)

2005-01-24 Thread snekse
Thanks for your response. It was helpful since it brought up some other instances that I hadn't really thought of, such as allowing a double submit for certain actions. > > Here is the flow we have for this application. > > > > 1. User searches for a profile > > 2. List of matching profiles is d

Re: Where to send !isTokenValid(request)

2005-01-21 Thread Kishore Senji
On Fri, 21 Jan 2005 16:26:51 -0600, snekse <[EMAIL PROTECTED]> wrote: > I have a Best Practices type question. Where should I send the user > if isValidToken returns FALSE? This is the sort of question you should be asking yourself or probably your business analyst. What do you want to do when th

RE: Where to send !isTokenValid(request)

2005-01-21 Thread Karr, David
I haven't had a lot of opportunity to validate this strategy, but I believe you have the right idea. Conceptually, the result from a double submit should just look as if it was a single submit. So, the second submit would bypass the processing logic and just forward to view the results that were