Reconnecting

Connections drop: Wi-Fi changes, the lid closes, a server restarts. etrans notices and gets the connection back on its own.

Noticing

• A connection the server or the network closes is noticed within two seconds.
• A connection that goes silent — the usual state after sleep, when the socket still looks open and nothing answers — is found by a small request every sixteen seconds. If it gets no answer within eight, the connection is treated as gone.

Getting it back

A strip under the toolbar says The connection to web-1 was lost. Getting it back…, then Trying again (attempt 3)… with the last reason it failed. Attempts come at once, then after 1, 2, 4, 8 and 15 seconds, and then every 30 seconds.

• Try Now tries at once instead of waiting.
• Disconnect gives up and goes back to the server list.

etrans stops trying by itself when the server refuses the login or the host key — trying again would not help — or after about twenty minutes. The strip then offers Reconnect to try again by hand.

A password you typed for the connection, without keeping it in Keychain, is remembered for the window, so getting the connection back does not ask again. A one-time code is asked for again, since it would not work twice.

What comes back

• The server pane, in the folder it was in, listed again.
• The forwards that were running.
• The transfers that were running when the connection went: they carry on from their partial files, without you pressing anything.
• Files open for editing upload over the new connection when you save them.

Terminals do not come back; open a new one.