[Interest] QNAM timeout is way too long

Jason H scorp1us at yahoo.com
Mon Apr 21 21:19:21 CEST 2014


It should be 75 seconds on most platforms. You can blame that on ARPAnet.

I've implemented shorter timeouts without issue. You wouldn't want to use abort anyway, you'd want to make a new one called "timeout" since aborts happen for other reasons.




________________________________
 From: Scott Aron Bloom <scott.bloom at onshorecs.com>
To: "<interest at qt-project.org>" <interest at qt-project.org> 
Sent: Monday, April 21, 2014 1:28 PM
Subject: [Interest] QNAM timeout is way too long
 


 
I have code, that sends a http request via  QNetworkAccessManager.  Unfortunately, there are times, where the network on the machine will be up, but the connection to the internet is down.. Or the internet is up, but the backend server is down.  Meaning, there is no way for my application to “know” don’t bother trying to connect.
The problem, the timeout for the request, before failure seems WAY WAY too long, upwards of 30 seconds.
 

Is there any way to reduce this??  It’s a very very fst request, a 3-5 second timeout, would actually be fine.
 
Any thoughts???

Scott
 
 
_______________________________________________
Interest mailing list
Interest at qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20140421/c07096e1/attachment.html>


More information about the Interest mailing list