Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!bu.edu!att!emory!rsiatl!meo
From: meo@rsiatl.UUCP (Miles ONeal)
Newsgroups: comp.windows.x
Subject: Re: R5 wish list -- client recovery
Message-ID: <4972@rsiatl.UUCP>
Date: 19 Nov 90 03:55:22 GMT
References: <6220@lanl.gov>
Organization: Rapid Deployment Systems, Inc. (making go fast things and things go fast)
Lines: 27

I agree. In fact, ideally, I want both (well, of *course*
you do - here, have a bridge, too).

When timeout is selected (known by server, who tells client
at connect, if they are R5 or later, anyway - also settable
via client command line?), each client polls the server (or
expects a watchdog signal from the server - I don't care)
every n minutes (def = 10? - also user selectable). If the
test fails x times in a row, the clients give up and grace-
fully go away.

Alternatively, when the server comes up, it announces who it
is (say, fred:0) on the usual well known socket, and anybody
who thought they were already talking to fred:0 reattaches,
and the server sends them an expose event. Could be annoying
with bogus unix:0 announcements, but so is having to go find
and kill 20 processes when someone is debugging their login
on a new x terminal that refuses to work like the old one did.

User selectable as to which behavior is desired, of course.

-Miles

Miles O'Neal
{uunet | emory}!rsiatl!meo (home)
meo@sware.com              (work)
{uunet | emory}!sware!meo  (work)