0

I have a .NET (3.5) webform-based web application. The software runs on different IIS servers and relies on connection towards external resources (db, sftp, sharepoint). The point is: the network literally s**ks, but I have no control on it so I have to do my best in developing.

As the network lacks in responsiveness, it could take seconds to get the response on a submit, and sometimes user tends to re-click the submit button, generating server-side a duplication of post back events that ends up with broken data and application.

I applied this solution to avoid double-clicking, but it doesn't fit properly my requirements as sometimes I simply can't get any feedback or event to re-activate the submit button (for instance: download a file).

I wonder there's a more solid solution (for example: can I identify an incoming postback, to block it if I recognise it to be doubled?)

Any idea is welcome

(A beer in Rome for the best answer is ensured ;) )

Thanks

Damon
  • 3,004
  • 7
  • 24
  • 28
balanza
  • 1,059
  • 1
  • 12
  • 34

1 Answers1

0

A really simple solution to this is just to disable the button when it's been clicked (I've had to do something similar in most of my applications). There's plenty of articles with source code about this on the web for example this one

This has also been addressed in many question on SO. See here and here.

Community
  • 1
  • 1
Damon
  • 3,004
  • 7
  • 24
  • 28
  • Hi, client-disabling the submit button is the solution that's now in production, but it's not enough. I wanted something more "native" for .NET framework, but I realize that there's no other way that implement this by myself. I'm moving towards validating or not the request once it arrives on the web server, I'll let you know – balanza Dec 09 '13 at 01:52