iddqd345 0 Posted October 9 Why did tHttpCli.Timeout start to be calculated in seconds instead of milliseconds in version 9.1? I need a HttpRect timeout of 1500 milliseconds. I don't see any problem with adding, for example, the TimeoutMsec property and changing THttpCli.DoRequestSync, but was there a important reason for changing it to seconds? Share this post Link to post
Angus Robertson 696 Posted October 9 That change to seconds was internal only, the public TimeOut property has always been seconds, or at least since V7.04. If you need millisecond precision, I suggest you copy the procedure DoRequestSync to your application, adapt it, and use it after an async method call. Angus Share this post Link to post