> A object created in ASP by Server.CreateObject() and used on only a single
> page only needs apartment threading model, so critical sections
> etc are not
> required. - The object is created and thrown away at the end of each page.
> With Object pooling it is possible that the object is not thrown away but
> deactivated instead and put into the object pool, so the same rules will
> still apply.
>
> 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.
Didn't MS drop object pooling in COM+ (and it never was in MTS)????
Something along the lines of "not able to get it to go" before the release
of 2k.
> 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.
Sounds like a more feasable solution.
--
Nic Wise - 021.676.418 / [EMAIL PROTECTED] / Inprise/Borland New Zealand
Is it not a foolish man, said little Woo, who keeps all his chickens in his
trousers?
For at best, will he not suffocate his chickens, and, and worst, will he not
disappoint the ladies in the village? --Alexi Sayle
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
