i have one multi line text box and one save button..
When a SAVE button is pressed it will perform a action on the
database either to add data that a user has entered.
When the refresh button is pressed at the top of the page the same
exact data is re-submitted again resulting duplicate transaction in the
database. Is there anyway of stopping this happening? From client-side
script or server side , how can we detect that the "Refresh" button is click?
When you know for sure that the users are bound to click the browser's refresh button to refresh the screen, why not put a refresh button on screen along side the data that they expect to be updated and perform a refresh of just that data?
That was just a suggestion to improve your application. Now to the solution to your problem.
Once the save is completed, just register a client script that would make a fresh request for the page. You can do so by calling window.location.reload() or window.location.url='PageName.aspx';
This would refresh the page and the next time Refresh/F5 is hit only page load is posted not the button click.
we are developing an application in ASP .NET. Every connected client is downloading a small file (about 12kb) every second. This file is changed every second by a multithreaded application.
We have dedicated server for this solution, but it performs really bad when there are about 100 clients connected.
My questions is: could this performance problem be caused by downloading this small file so often?