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?
Right having thought about this a bit more, I realize my pseudo code was a bit off. You're close though, you just need to split _mainstr into an array too then iterate through that and iterate through your _substr array too so:
Loop through _mainstr array
Within each loop, loop through _substr array and see if it's there, if so, add to holding object.
Holding object at the end = matched items in the original order.