[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mutt-dev
Subject:    Re: Add $socket_timeout configuration option.
From:       arnt () gulbrandsen ! priv ! no
Date:       2015-08-20 21:13:24
Message-ID: IImUuyPsFFaOg8N2s4vjpYQor/4WzI3Fc79o3PmLXRU=.sha-256 () antelope ! email
[Download RAW message or body]

I implemented something similar for another client and disagree 
viciously ;) The proper timeout depends in the network, and asking the 
user is a cop-out.

I am currently on vacation at a farm in Italy, very 
nice and not just because of the free wlan, but the configuration of 
the network here is not a user matter. You do not want to reconfigure 
mutt to go on vacation. (Or perhaps you do, but let us pretend you 
don't.)

A much better approach is to count seconds of connection 
idleness, and after a few tens of seconds to mark the connection as 
unreliable. When using an unreliable connection, the first command must 
be a noop with a strict timeout.

Arnt
[prev in list] [next in list] [prev in thread] [next in thread]