Women in Technology

Article:		Handling Multiple Submits
Subject:		Can any one explain me how this solves the problem???
Date:		2003-04-09 19:42:08
From:		tarkesh_rokala

Showing messages 1 through 3 of 3.

• Can any one explain me how this solves the problem???
  2003-04-10 11:38:22  anonymous2 [View]
  
  
  Well basically, you're synchronizing your requests based on a session identifier. This is similar to the way you might handle the problem if you were writing your own multi-threaded server application, and you had to make sure that you knew where requests originated from.
  
  This solution also assumes that session state tracking has been started prior to the form submission, or you're really no better off -- each new form submission would then get a new session.
  
  
• Can any one explain me how this solves the problem???
  2003-04-10 14:42:28  anonymous2 [View]
  
  
  I guess it does not solve the problem. What if the servlet redirects to the same page? Then the user would be able to do it again and again. Some token has to be put in the session so the servlet knows the request has been sumitted.

• Once you've identified the requests you don't want to process - what is the best way to 'kill' them?
  2003-04-10 08:29:53  anonymous2 [View]
  
  
  We are looking at several duplicate requests coming in. We want to process the first but ignore the subsequent ones - i.e. just return a response to the client for the first request.
  We can identify the duplicate requests - but how do we actually deal with them.