Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!mcsun!unido!laura!tommy!klute
From: klute@tommy.informatik.uni-dortmund.de (Rainer Klute)
Newsgroups: comp.windows.x
Subject: Design problem with XSetIOErrorHandler
Message-ID: <2959@laura.UUCP>
Date: 23 Jan 91 10:47:57 GMT
Sender: news@laura.UUCP
Reply-To: klute@tommy.informatik.uni-dortmund.de (Rainer Klute)
Organization: University of Dortmund, Germany
Lines: 25

May I cite from the Xlib MIT X Consortium Standard on XSetIOErrorHandler:

	"The XSetIOErrorHandler sets the fatal I/O error handler.
	Xlib calls the program's supplied error handler if any sort
	of system call error occurs (for example, the connection to
	the server was lost). This is assumed to be a fatal condition,
	and the called routine should not return. If the I/O error
	handler does return, the client process exits."

I wonder why the Standard considers I/O errors "fatal" and the why the X
client has no other chance than to quit execution.

The application I am writing wants to deal with I/O errors itself - and in
quite another way than exiting. Especially the example quoted from the
Standard (connection to server lost) is the problem I want to handle. My
application opens connections to several servers, and if one of them breaks
the program is still able to operate. So why should it exit?

Any comments?

-- 
  Dipl.-Inform. Rainer Klute      klute@irb.informatik.uni-dortmund.de
  Univ. Dortmund, IRB             klute@unido.uucp, klute@unido.bitnet
  Postfach 500500         |)|/    Tel.: +49 231 755-4663
D-4600 Dortmund 50        |\|\    Fax : +49 231 755-2386