Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!ccut!wnoc-tyo-news!dclsic!sjc!leia!harkcom From: harkcom@spinach.pa.Yokogawa.CO.JP Newsgroups: comp.windows.x Subject: Re: resource ID allocation Message-ID: Date: 13 Feb 91 22:27:05 GMT References: Sender: news@leia.pa.yokogawa.co.jp Distribution: comp Organization: Yokogawa Electoric Corporation, Tokyo, Japan Lines: 22 In-reply-to: harkcom@spinach.pa.Yokogawa.CO.JP's message of 9 Feb 91 02:53:55 GMT In article harkcom@spinach.pa.Yokogawa.CO.JP (that's me) writes: =} But what I don't understand is what happens if a client continues =} creating and destroying resources to the point of using up all of the =} valid ID's. Does X have some mechanism for resetting the resource_id =} member when it overflows into the SERVER_BIT? If not, clients which =} manage a lot of resources for a long time may run out of valid ID's. =} =} If such a mechanism doesn't exist, has there been any talk about =} implementing a feature which allows the re-use of 'used' resource ID's? Since there were no replies, I figure nobody knows. I checked Xlib and could find nothing that does such a thing. I also discovered that there is no mechanism for setting your own ID when making a request to create a resource. The client just keeps sucking up valid ID's until there are none left and them is completely helpless... If I am wrong about this, please, PLEASE, somebody tell me before my next free Friday night, or I might just create a support library to handle this. BTW: How does one go about suggesting to the powers that be that this might be a good addition to Xlib. [for ex. XReCreateWindow(Display *, XID)]