Comment by ChrisMarshallNY
4 hours ago
The problem with doing that, is that the standard TCP timeout is 60 seconds.
All of a sudden, you are beset with 60-second hangs.
4 hours ago
The problem with doing that, is that the standard TCP timeout is 60 seconds.
All of a sudden, you are beset with 60-second hangs.
If the computer doesn't have any online network connection, shouldn't it outright error? I understand that the timeout sucks when your network is not connected to the internet but still alive, then that's an issue, but if there is no connection at all, why would the timeouts matter?
You just gave me flashbacks of mistyping a folder share name on windows and having the whole PC lock up for a minute or two.
> All of a sudden, you are beset with 60-second hangs.
No, that's not how it works. Frankly, I'm astonished to see this claim here.
The problem with this is some apps do incredibly stupid things. Now I'm not saying the operating system itself, but I had some ide screw off and go into long pause mode when my laptop was in airplane mode.
I'm sure there are stupid apps out there, but "the standard TCP timeout" was a misdiagnosis of the problem.
Depends.
I have a couple of apps on my computer that do exactly that.
I am looking forward to learning how it does work...
> I am looking forward to learning how it does work...
It's basic sockets. If you call connect() when the internet is disabled, the errno is ENETUNREACH.
The higher-level API are built on sockets. If any apps are misbehaving, they're simply badly coded.