G grafsoft Well-Known Member Licensed User Longtime User Jan 10, 2016 #1 I do a poststring to my servwer, which runs without fault. In 2/3 of the tests, it takes 2-5 seconds to get the answer and everything runs smoothly. In 1/3 I get a timeout after 12 minutes. I could check with a timer, and after 10 Seconds "cancel" this job and start a new. But how? Should I simply do a new poststring with this httpjob and ignore the timeout?
I do a poststring to my servwer, which runs without fault. In 2/3 of the tests, it takes 2-5 seconds to get the answer and everything runs smoothly. In 1/3 I get a timeout after 12 minutes. I could check with a timer, and after 10 Seconds "cancel" this job and start a new. But how? Should I simply do a new poststring with this httpjob and ignore the timeout?
Erel B4X founder Staff member Licensed User Longtime User Jan 10, 2016 #2 The default timeout is set to 30000. I guess that the connection is successful but it then stalls for some reason. grafsoft said: Should I simply do a new poststring with this httpjob and ignore the timeout? Click to expand... Yes. Upvote 0
The default timeout is set to 30000. I guess that the connection is successful but it then stalls for some reason. grafsoft said: Should I simply do a new poststring with this httpjob and ignore the timeout? Click to expand... Yes.