Idle Users

[Fairlight]

Simon--er, no...it was Bob Rasmussen--said:
> 
> I can address the issue of preventing the problem from occurring. If you
> run Anzio Lite or AnzioWin (our products) as your telnet client, you can
> "disable quit" in Edit:Advanced options. This disables both the "X" box
> and the File:Quiet menu item. The user would then quit by exiting from
> their session at the Unix level.

Why not just handle the WM event gracefully?  

I just tested something with Perl/Tk.  If I bind to <Destroy> on the
top-level window, when I click on the 'X' icon, I -do- get a destroy event.

Now while I realise that C is not perl, both perl and pTk are written -in-
C, and therefore there is a mechanism by which they can pick up on the fact
that this has been activated and do something about it.  The very fact that
I can not only trap the event but also print the fact that I got the event,
then cause it to sleep afterwards without the program terminating indicates
that the 'X' button is -not- destructive in and of itself (such as a kill
-9 would be in *nix), as well--in fact, the window remains until I'm done
with my callback and -then- my program exits after handling all Destroy
events I have bound.

This is not conjecture.  I just tested, and it works fine all the way back
to win95b.

So if the facilities are there as they must be in C for pTk to accomodate
this behaviour, why would anyone take half-measures?  Just politely close
out the session in the ssh or telnet protocols before exiting.  Seems
simple enough, and frankly seems like the correct way of doing it.

mark->
-- 
Bring the web-enabling power of OneGate to -your- filePro applications today!

Try the live filePro-based, OneGate-enabled demo at the following URL:
               http://www2.onnik.com/~fairlite/flfssindex.html