:[EMAIL PROTECTED]
Sent: 18 February 2004 18:14
To: Tomcat Users List
Subject: Re: Stopping repeating requests
Phil,
True. I should have not said all client side. How about client side
validation?
Point being as weather to handle it more from the client or server. All
depends on application.
Doug
Another solution is to have a hidden field in the form which uniquely
identifies the form
submission request. When the form is submitted to the server, the server
side code can
process the request and maintain a list of processed form request
identifiers for this client
session. When the form
Hi!
Peter Guyatt wrote:
I have a problem where a user enters data into a form and then submits this
to the server, which in turn wrights this content into a database.
The problem I have is that if the user then refreshes the page via F5 then
it adds the same data in again.
Is there any way to
On submit of the form, show a dialog box and prompt the user to submit
the data. Then you can clear the data from the page.
Best regards,
Abhilash John
-Original Message-
From: Peter Guyatt [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 18 February 2004 10:48 PM
To: Tomcat Users List
Pete,
When the user submits the page where is the user sent?
If he stays on the same page and the form stay populated you need to do some
checks for change in a field before allowing the page to submit again. The
better way is to clear the form or send them to another page. That's all
client
Howdy,
I have a problem where a user enters data into a form and then
submits
this
to the server, which in turn wrights this content into a database.
The problem I have is that if the user then refreshes the page via F5
then
it adds the same data in again.
Is there any way to ensure that
Hi!
Parsons Technical Services wrote:
The
better way is to clear the form or send them to another page. That's all
client side.
Not necessarily. What I do in such situations is this: have a servlet
process the form data and then send something else (e.g. an update
successfull-page) as response
I use a system where a servlet sets a 'token' (a random number attribute)
which the JSP must return (using a hidden form field attribute) to the
servlet when the form is submitted.
The servlet keeps a copy of the token. The servlet checks the token sent by
the JSP with its own (current) copy. If
Phil,
True. I should have not said all client side. How about client side
validation?
Point being as weather to handle it more from the client or server. All
depends on application.
Doug
Hi!
Parsons Technical Services wrote:
The
better way is to clear the form or send them to another
