Re: Connection pooling
From: Michael D. Long (michael.d.long-nospam_at_comcast.net)
Date: 08/26/04
- Next message: Steve W: "Re: Oracle ADO query shows deleted records"
- Previous message: William \(Bill\) Vaughn: "Re: Connection pooling"
- In reply to: Jim Cutler: "Connection pooling"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 25 Aug 2004 20:37:20 -0400
Obviously what you want to do can be done - look at how MTS/COM+ objects
interoperate with the connection pool. It really sounds like what you are
trying to accomplish is already available with little or no effort on your
part other than to make ADO open and close calls appropriately. The
connection pooling algorithm is fairly simplistic, but it will maintain a
pool of connections as long as at least one connection remains open in your
process.
-- Michael D. Long Microsoft MVP - Windows SDK "Jim Cutler" <JimCutler@discussions.microsoft.com> wrote in message news:655B5B83-18D0-46A0-999E-274BE2FB8AAA@microsoft.com... > I am using C++ 6.0. I am writing a DLL to be called by another app. That > app currently creates a pool of connections during initialization and then > temporarily handing out connections to worker threads (which come and go). > Are there any issues involved in using an ADO connection from a thread that > did not actually open the connection? In other words, does the process of > opening the connection configure the thread in some way that will be missing > if another thread tries to use the connection?
- Next message: Steve W: "Re: Oracle ADO query shows deleted records"
- Previous message: William \(Bill\) Vaughn: "Re: Connection pooling"
- In reply to: Jim Cutler: "Connection pooling"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|