|
-
December 13th, 1999, 01:59 PM
#1
Designing/Implementing Database Component
I am trying to design a database component that could be simultaneously accessed and shared by multiple clients. For instance I want to create a component that has an ADO Connection object as one of its attributes that would be initialized when the first client needed to access the database, and destroyed when the last client released the object. If anyone could point me in the right direction, I would really appreciate it.
Thanks
-
December 14th, 1999, 09:59 AM
#2
Re: Designing/Implementing Database Component
Check out Microsoft Transaction Server available for free download from the microsoft site in an NT 4 service pack, but it works on win9x as well.
I think what your talking about is called object pooling. This is not availabe in MTS for win9x but MTS will create and destroy your object as needed or according to your settings. In Win 2000 MTS has been integrated with COM+ and does support object pooling.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|