On Sat, 19 Feb 2022, Carlos E.R. wrote:
> This has a problem. When doing a long operation (I think it is a search
> running on the server), I have to say yes to continue several times,
> because the server is indeed busy.
TLDR: If you know why you have a timeout, you can ignore it or keep the
connection open until the operation completes.
I agree that there are problems. The problem really stems from having this
option at all. You can either programmatically close a connection when it
does not reply automatically, or you can have the user tell you when too
much is too much. Apline does the latter, and the problem with this is
that some operations are slow (sorting, searching, etc.) and for them you
will probably timeout in some moment. It is hard for anyone to distinguish
if the delay is due to a bad connection or a slow operation.
Because of that, I never answer the timeout question the first time when I
am doing a slow operation, and just let Alpine continue, or always answer
no, if I feel I need to. If the operation takes too long I will interrupt
the operation, but most times I do not have to do anything. I just know
that I might get the question about breaking the connection closed and
just simply ignore it.