Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!uunet!tdatirv!sarima
From: sarima@tdatirv.UUCP (Stanley Friesen)
Newsgroups: comp.windows.x
Subject: Re:  resource ID allocation
Message-ID: <141@tdatirv.UUCP>
Date: 15 Feb 91 16:02:16 GMT
References: <9102140823.AA17984@lightning.McRCIM.McGill.EDU>
Reply-To: sarima@tdatirv.UUCP (Stanley Friesen)
Organization: Teradata Corp., Irvine
Lines: 14

In article <9102140823.AA17984@lightning.McRCIM.McGill.EDU> mouse@lightning.mcrcim.mcgill.EDU writes:
|... "should not" because creating 262144 resource objects over the life of
|a program seems a bit excessive.  But if you must, you *can* reuse
|XIDs.  (If you have a client that is perverse enough to want to have
|more than 262144 resource objects in existence simultaneously, you will
|most likely have trouble.

You will likely have more trouble than just XID availablility!  I seriously
doubt that there are any existing X servers that can provide that many
simultaneous X resources anyhow.  [i.e. you will get a BAD_ALLOC error
long before reaching 262144 XID's].
-- 
---------------
uunet!tdatirv!sarima				(Stanley Friesen)