Path: utzoo!attcan!uunet!lll-winken!ames!sun-barr!decwrl!wam.UMD.EDU!stripes
From: stripes@wam.UMD.EDU
Newsgroups: comp.windows.x
Subject: Re: Handling Errors w/ Multiple Connections
Message-ID: <8905242051.AA19935@cscwam.UMD.EDU>
Date: 24 May 89 20:51:00 GMT
References: <8905240252.AA17419@cscwam.UMD.EDU> <8905241312.AA00893@expire.lcs.mit.edu>
Organization: (very little)
Lines: 18

In article <8905241312.AA00893@expire.lcs.mit.edu> rws@EXPO.LCS.MIT.EDU writes:
>"Recover" is an undefined term.  Without understanding the requirements for
>recovery, and how universal they are, it's not prudent to design a mechanism to
>handle it.  I've seen no attempts to establish requirements in this area.

  All the "recovery" I want is to be able to continue useing the OTHER
connections, which have had no IO errors.  As an example think about a Xclient
that allows more then 2 users to "talk" to each other, this client opens one
connection to the display of each person invovled.  With the current handleing
of XKillClient, and IO errors if one user kills his talk with a window manager
insted of exiting the application it will kill EVERYONE's talk.
  If the client could continue to use the other displays it could react as if
the user had quit, insted of dissapearing from the displays of all the other
users (with no explination).
-- 
           stripes@wam.umd.edu
      Josh_Osborne@Real_World,The
      "The dyslexic porgramer"