Re: ICCCM compliance questions

Article View: comp.windows.x

Article #36575

#36575

From: Donna Converse
Date: Thu, 08 Feb 1990 20:42

17 lines
1332 bytes

> I have noticed that certain clients generate output on the console when
> 'Quit'ing out of them via olwm (broken pipe from server).  XView-based clients
> do not (and certain other well-behaved clients do not).  I suspect the error
> message is due to non-ICCCM compliant clients.  What kind of changes should
> be made to clients who exhibit this problem?

Although I am not sure what "'Quit'ing out of them via olwm" really means,
I can say that well-behaved clients participate in the protocol described
in section 5.2.2 of the ICCCM, that is, they delete their own windows when 
requested.  If clients don't participate in the window deletion protocol,
the window manager may "kill" them, meaning, disconnect them from the server.
The server disconnect results in the console broken pipe message.


Donna Converse
converse@expo.lcs.mit.edu

Technical Details

Message-ID: <9002082042.AA09006@expo.lcs.mit.edu>

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!munnari.oz.au!uhccux!ames!think!mintaka!bloom-beacon!EXPO.LCS.MIT.EDU!converse

References: <295@venice.SEDD.TRW.COM>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!munnari.oz.au!uhccux!ames!think!mintaka!bloom-beacon!EXPO.LCS.MIT.EDU!converse
From: converse@EXPO.LCS.MIT.EDU (Donna Converse)
Newsgroups: comp.windows.x
Subject: Re: ICCCM compliance questions
Message-ID: <9002082042.AA09006@expo.lcs.mit.edu>
Date: 8 Feb 90 20:42:03 GMT
References: <295@venice.SEDD.TRW.COM>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 17

Reply to Parent Message