Closed PropGit closed 8 years ago
The connect() socket function doesn't seem to have a timeout parameter. I'll have to check to see how a timeout can be specified for it.
Maybe there's no was to adjust this, and I can't tell if it's directly related to that either; just pointing out something that we may be able to optimize. If any part of the communication has reached a point of no return, significant additional delay before the user can try something else only leads to user frustration.
Changed the connect timeout for HTTP requests to 2 seconds.
I experienced a delay > 20 or 30 seconds before the connect failed message in the following results:
Note: The module was having occasional loss of association near this time, which may account for the extra delay; however, if we could shorten the timeout to something more reasonable (thinking there's no possibility of recovery after a certain short period (seconds)), that would be wonderful.