Have tried using isTokenValid()/resetToken()/saveToken(). The above works.. i am able to differentiate between the first and the successive http request's.

Question is .. what to do with the successive request that come in ??

That's a bit of a strange question to ask. You're able to differentiate between the first and any subsequent submits - great, that's what you want to be able to do. What exactly should happen for the second request is a matter of your business logic (or how user-friendly you want to be). So, "what to do with the successive request that come in" is a question for you.

Navi Lock
Ranch Hand

Joined: Jul 29, 2003
Posts: 39

posted Nov 23, 2007 18:41:00

0

HI Ulf, Thanks for responding..

I still want the customer to see the result page only invoked due to the first 'submit'. Is there a way to ignore the successive submit request's?

That is what i wanted to do.. need to know how to do the above.

Thanks again, -Navi

Navi Lock
Ranch Hand

Joined: Jul 29, 2003
Posts: 39

posted Nov 24, 2007 20:34:00

0

Any other suggestions guys ??

Thanks, -Navi

Ulf Dittmer
Rancher

Joined: Mar 22, 2005
Posts: 42954

73

posted Nov 24, 2007 23:25:00

0

I still want the customer to see the result page only invoked due to the first 'submit'. Is there a way to ignore the successive submit request's?

Once again, you said you knew how to differentiate between the first and subsequent requests. So what prevents you from ignoring subsequent ones?

Navi Lock
Ranch Hand

Joined: Jul 29, 2003
Posts: 39

posted Nov 26, 2007 00:00:00

0

Yes.. that is what i want to know.. How to ignore the subsequent requests..

what are/is the way to ignore the subsequent request's?? Or rephrasing - How to kill/nullify the subsequent request, while the first request is still being processed and hasn't reached a decision point.

I would like to show the result page based only on the first request only..

I missed this thread when it was first posted...I think I was out eating Turkey!

A few years ago I played with trying to get token working in my application to prevent double submissions. One of the major issues for me is the one mentioned in this thread. I ended up going with a client-side JavaScript solution that works good enough.