Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!decwin.DEC.COM!fisher
From: fisher@decwin.DEC.COM (VMS DECwindows Engineering, 381-1466)
Newsgroups: comp.windows.x
Subject: RE: GrabServer/UngrabServer nesting?!?
Message-ID: <8904141722.AA25719@decwrl.dec.com>
Date: 14 Apr 89 17:22:47 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 16

Well, I agree with your sentiments, and if this were 2 years ago, I would
push for the change.  Now, however, there may well be applications which
depend on the existing behavior.  I don't think we can just change the
protocol out from under everyone.

I think that now, the right solution is to add an Xlib call 
XGrabServerNested or some such which does the ref counting as
I suggested before.  One would have to define how it works with the normal
old XGrabServer, and whether there is an XUngrabServerNested, or whether the
existing one will suffice.  This solution fits much better into the X 
philosophy:  Let the client do any work that it can.  Note that most if not 
all of the hair that is in the protocol relates to inter-client issues.  
There is little if any help for individual clients.  (Note, for example, the
lack of a GetGC).

Burns