On Fri, 5 Jan 2001, Gunther Birznieks wrote:
Sorry if this solution has been mentioned before (i didn't read the earlier
parts of this thread), and I know it's not as perfect as a server-side
solution...
But I've also seen a lot of people use javascript to accomplish the same
thing as
Stas Bekman [EMAIL PROTECTED] wrote:
On Fri, 5 Jan 2001, Gunther Birznieks wrote:
Sorry if this solution has been mentioned before (i didn't read the earlier
parts of this thread), and I know it's not as perfect as a server-side
solution...
But I've also seen a lot of people use
James G Smith [EMAIL PROTECTED] wrote:
Stas Bekman [EMAIL PROTECTED] wrote:
On Fri, 5 Jan 2001, Gunther Birznieks wrote:
Sorry if this solution has been mentioned before (i didn't read the earlier
parts of this thread), and I know it's not as perfect as a server-side
solution...
But I've
Does anyone out there have a clean, happy solution to the problem of users
jamming on links buttons? Analyzing our access logs, it is clear that it's
relatively common for users to click 2,3,4+ times on a link if it doesn't
come up right away. This not good for the system for obvious reasons.
I
"Ed" == Ed Park [EMAIL PROTECTED] writes:
Ed Has anyone else thought about this?
If you're generating the form on the fly (and who isn't, these days?),
just spit a serial number into a hidden field. Then lock out two or
more submissions with the same serial number, with a 24-hour retention
of
Sorry if this solution has been mentioned before (i didn't read the earlier
parts of this thread), and I know it's not as perfect as a server-side
solution...
But I've also seen a lot of people use javascript to accomplish the same
thing as a quick fix. Few browsers don't support javascript.
- Original Message -
From: "Ed Park" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, January 04, 2001 6:52 PM
Subject: getting rid of multiple identical http requests (bad users
double-clicking)
Does anyone out there have a clean, happy solution to the proble
