0

I'm doing some automation using a localhost address, so if a request takes quite a bit of time to process, it's almost guaranteed that it will not complete and will time out. Waiting for that to happen, not being able to make another request at the time is not cool.

I'd like to be able to predict if a request is timing out and cancel it. It's usually completed in under 6ms. I suppose I could use StopWatch to monitor the time, but how do I continuously check if it's time to cancel current request and start a new one?

Currently, I'm just running a Timer with 50ms interval and do BeginInvoke on the update method. When a request times out, my app freezes for a bit, and when several requests in a row time out, freeze times stack and freezing becomes very noticeable. So I thought I should somehow limit simultanous requests to just one at a time and restart it whenever it takes too long, but I have no idea how to code that.

user1306322
  • 8,561
  • 18
  • 61
  • 122
  • 1
    You most likely just want to set the timeout. See [How to change the timeout on a .NET WebClient object](http://stackoverflow.com/questions/1789627/how-to-change-the-timeout-on-a-net-webclient-object). – CodeCaster Feb 27 '14 at 14:55

1 Answers1

2

You have two options.

1) You could move to a WebRequest/WebResponse design since WebRequest objects have a Timeout property which you can set.

2) Alternatively you can create a custom WebClient class overriding its GetWebRequest method and specifying the timeout there.

coolmine
  • 4,427
  • 2
  • 33
  • 45