If any reader is aware of how to achieve this within acceptable limits of programming complexity, I will be happy to revise this paragraph to reflect the same. Whether these objects will satisfy all the requirements for Object Pooling is a question that will have to wait until a preview version is available. This is an environment that I have never used for COM development and hence cannot verify if it can be used to develop pooled objects. The Platform SDK for Windows 2000 RC2 does have a Java sample, which leads me to believe that this environment can be used to develop COM objects that can be pooled. The title of this section serves to alert the reader to this very fact and provides some practical guidelines on when to use this service.
Clients use the pooled objects briefly and in rapid succession.
The benefits resulting from using Object Pooling must be thoroughly evaluated by testing the client application to use the object being pooled with and without this service. Another important consideration is to determine meaningful values for the various pool characteristics. Values for the 'Minimum pool size', 'Maximum pool size' and 'Creation timeout' will vary from application to application. Some factors that affect these values are hardware configuration, available precious resources, average number of clients, average client access time, maximum number of clients and expected response time. It has clearly outlined the requirements for COM objects that can be pooled and also cautioned the reader to the fact that Object Pooling is not the silver bullet for achieving improvements in performance and scalability.