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: resource ID allocation
Message-ID: <HARKCOM.91Feb8215355@spinach.pa.Yokogawa.CO.JP>
Date: 9 Feb 91 02:53:55 GMT
Sender: news@leia.pa.yokogawa.co.jp
Distribution: comp
Organization: Yokogawa Electoric Corporation, Tokyo, Japan
Lines: 23


   I've been pondering the allocation of resource ID's.

   I understand how a window allocates an ID and sends a request
to the server for creating new resources. I also understand that
the server checks to insure that the id is a valid one.

   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?

thanks
Al

P.S. One must be either extremely bored or extremely ex[c]ited by such
a topic to actually spend a friday night digging through source code.
Well, nobody's asked me go out for a beer so I think I'll keep reading
source. It's cheaper than paperbacks in this 'greedy' country...