Re: Double click

Tech-Archive recommends: Fix windows errors by optimizing your registry


"Jeff" <gig_bam@xxxxxxxxxxxx> wrote in message
news:KIWdnT2ZLriTKzHfRVn-sw@xxxxxxxxxxxxxxx
> Thanks for your NOT SO FRIENDLY response. I thought, since the form is
> written with asp, and it submits to an asp page, and the results are
> displayed with asp, that this was the place to ask. I didn't see a NG
> labled submit buttons.
> I know that most in here, if there was a solution, would give it.
> Therefore, I do not accept your response, and will wait patiently to see
> if someone can help me.

Don't mind him, he's just the resident know-nothing ***-head. Whatever
glimpse of programming he may have once had is now eclipsed by a bad
personality and a tendency to be wrong much of the time. (I suspect there
may be a language barrier issue as well, but his level of arrogance isn't
usually present in such cases, so the jury is still out on that score.)

I'm going to assume that by "double click" you mean double submit, where the
user clicks the submit button a second time, before the first request has
been delivered to the user's browser, but after the first request has been
received by the server.

Unfortunately there isn't a bunch you can do about this on the server side.
You might try time-stamping the requests as they come in, and discarding ant
that are received within a certain proximity, but this can be difficult to
do, depending on the processing that's involved.

There is of course the widely used "social engineering" scheme (i.e., the
'do not press this button more than once' warning) but sadly it's less than
effective.

There are some client-side remedys, such as hiding the button after it has
been clicked, but before the request has been submitted (process onclick)
but I had 7 kinds of hell trying to make that work in non-IE browsers, and
finally gave up.

You might want to try clarifying you post (particularly if my assumptions
were incorrect) and resubmitting it to
microsoft.public.inetsdk.programming.scripting.jscript. There is a definite
server-side slant to your issue, and doubly-submitted requests surely can
cause database issues, but your most effective solutions are likely to
reside on the client end.


-Mark


btw, to any of you that might care to flame me for taking a shot at that
guy, first ask yourself, "does he have a valid point?" And second, be sure
to quote back the "offensive" part because that guy likely has me
kill-filtered, and I'd hate for him to have to wonder about what was said.


> "Evertjan." <exjxw.hannivoort@xxxxxxxxxxxx> wrote in message
> news:Xns9673F29B1D72Eeejj99@xxxxxxxxxxxxxxxxxx
>> Jeff wrote on 12 jun 2005 in microsoft.public.inetserver.asp.db:
>>
>>> This has probably been asked 100's of times, but I couldn't find
>>> anything on it.
>>>
>>> Is there a small script of some sort, that would disable the ability
>>> to double click a submit button>?
>>
>> ASP runs serverside and does know noting about clicking.
>>
>> Databases under ASP know even less.
>>
>> Please ask a apopriate clientside NG.
>>
>> --
>> Evertjan.
>> The Netherlands.
>> (Replace all crosses with dots in my emailaddress)
>>
>
>


.

Quantcast