This week's book giveaway is in the Agile and Other Processes forum. We're giving away four copies of Darcy DeClute's Scrum Master Certification Guide: The Definitive Resource for Passing the CSM and PSM Exams and have Darcy DeClute on-line! See this thread for details.
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.
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!