Ivan <ega_at_math.chalmers.se> writes:

> I still think that Coda is a step in the right direction, to make
> the functionality independent of the [presence of] communication channel.

Absolutely.

> It can (and probably should) be extended to behave well when other
> properties of the connection change, besides presence/absence.

I've gotten a bit further now: I've got a script triggered by the
change in carrier status on my laptop's ethernet interface, that
flushes the IP routing table and triggers a DHCP lease renewal.  Then,
the acquisition of the DHCP address lease triggers another script,
which stops the currently running Venus, and starts a new one.  The
result is that a new, working, connection is quickly established.

The down side is that I lose my Coda token, and have to run clog.

> P.S. I think "screen" and a reconnecting ssh-wrapper with authentication
> agent can achieve "connection persistency"-alike for terminal sessions...

Screen is your friend!  :-)

-tih
-- 
Tom Ivar Helbekkmo, Senior System Administrator, EUnet Norway
www.eunet.no  T: +47-22092958 M: +47-93013940 F: +47-22092901