Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!decwrl!wam.UMD.EDU!stripes
From: stripes@wam.UMD.EDU
Newsgroups: comp.windows.x
Subject: Handling Errors w/ Multiple Connections
Message-ID: <8905240252.AA17419@cscwam.UMD.EDU>
Date: 24 May 89 02:52:11 GMT
Organization: (Almost None)
Lines: 18


  I've been having a problem handleing "fatal" errors (like having the
client killed by the window manager).  The application could handle the
loss of a display connection (each connection is to a diffrent display),
but there is no way to recover from such errors, my documation says
that a handler set by XSetIOErrorHandler() can not return.  The best
way (that I have come up with) around it is to fork off a new process and
re-open the other connections, but that is a gross kludge at best.  Does anyone
else have a better kludge?  Should a KillClient cause an IO error, or is
this a bug in DEC's (not MIT's) X11R2 server?  Is there going to be a better
way to recover from such errors in future revisions of X?  Thanks for your
time...
-- 
           stripes@wam.umd.edu
      Josh_Osborne@Real_World,The
      "The dyslexic porgramer"
        "Bones, help this man, He's hurt!"
         "Dammit, Jim, I'm a DOCTOR, not a.... Oh, yeah."