On Wed, 9 Nov 2005, Bruno Aranda wrote:
I normally deal with that in the client side with a javascript function
that I put on the onclick and only allows to submit the form once.
Thanks, I'd forgotten about that solution.
A server aproach should be better though,
Yes, using JavaScript as duc* tape to hide a server-side problem isn't
ideal.
or maybe add that javascript to the extended commandLink/commandButton
(through a new parameter) so that using the t:commandLink avoid the
multiple submission problem by default?...
I'll have a go at doing this, perhaps with a configurable/optional timeout
since, as a user, I've been annoyed by sites that force you to reload the
page if the first submit doesn't work.
Jeremy
