The reason for our desire to disallow user-initiated disconnection via the
terminal emulator, as opposed to logging-out of the application cleanly
and then closing the emulator, is to prevent data corruption and to do
a bit of end-of-session work (cleanups, statistics logging, etc). 

Every so often, a couple of times a year, we get a data corruption from
a session not closing cleanly. This causes downtime of around 2 hours
while we recover the database from backup & transaction logfiles. We
have had the occasional major drama when this recovery didn't work
fully, but that's another story.

I know that we'll still get a lot of disconnected sessions due to network
initiated inactivity timeouts and communications problems, but this will
stop a large number of the disconnections that we experience.

As far as "unkillable" emulator windows left after a network disconnection,
what I suggest is a setting to disallow the user from disconnecting from
the host, including closing the emulator window while connected. This
would allow the emulator to be closed if a disconnection happened.

Greg.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *