Object pooling is back and working in Win2k, I have written some simple
tests and the concept appears to work well.
(I set a TimeCreated property in the initialization and set a TimeActivated
property in the Context.Activated method, I can then create the object from
a page, the two times will be the same first time round and the subsequent
calls show the time difference etc.)
> Depending on your licensing etc, you may still find a need to drop your
> connection when the object is deactivated. You have no control under
> MTS/COM+ of how this happens.
With pooling in COM+ you can monitor and control the max number of pooled
object etc, although this is not an issue with our license agreement
> The other alternative would be to create an Application level object that
> contains a list of available connections, and then each page level object
> asks your application object for a unused connection.
I had considered the creating an application connection pool of my own, but
then I really do need to control access and was not too sure if I need to
marshal the interface pointers etc (ie I became confused)
Neil
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
