Path: utzoo!attcan!uunet!ncrlnk!ncr-sd!hp-sdd!ucsdhub!sdcsvax!ucsd!rutgers!tut.cis.ohio-state.edu!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: destruction/freeing of XIDs
Message-ID: <8812231652.AA22295@EXPO.LCS.MIT.EDU>
Date: 23 Dec 88 16:52:02 GMT
References: <899@quintus.UUCP>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 20


    how far does this go?

No farther.

   If my process creates a pixmap and installs it as
   a property of a window, and another process finds that pixmap's XID and
   tries to free it, what happens?

The mapping between the id and the pixmap gets undone; if the pixmap itself
is stored in a GC or a window background, the pixmap will not get freed
until its reference count goes to zero.  The effect is no different than
if you had freed it.

   Do I have to worry about my resources
   being destroyed behind my back?

Depends on what you mean.  If you mean, should I worry about malicious
clients, the answer is no, at least not at the programming level, at
least not with the way X is defined today.