------- Comment #5 from  2009-05-07 03:11 -------
(In reply to comment #5)
> Because your solution doesn't solve even your problem.

Perhaps you would like to propose a better solution ? 

My original request was have some mechanism (not defined) to release resources
as soon as reasonably possible to prevent resource hogging.  

Perhaps if a object (e.g. buffer, lock, or handle etc) is defined, as a member
of a resource pool, then a resource process will wake-up every x.xx seconds (as
configured by the programmer) and remove any freed objects.

The programmer should be able to define multiple resource pools.

It would be desirable if the resource process could report how many resources
had been freed, every wake-up, or a defined period of time.   


Reply via email to