DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 4 of 4

Thread: connection pooling

  1. #1
    Guest

    connection pooling

    I have what I suppose is a basic question in regards to the way vb and OO
    works.

    How would I develop a class/set of classes for connection pooling (no, I
    don't want to use MTS)? Is there a way that a class can be instantiated and
    have that particular instantiated class available to all apps/classes that
    would like to use connection pooling? Or do I have to develop an app that
    instantiates the connection pooling class when the app is initiated and then
    destroyed when the app is closed?

    Thanks





  2. #2
    Richard Dalton . Guest

    Re: connection pooling


    <anthony> wrote:
    > I have what I suppose is a basic question in regards to the way
    >vb and OO works.


    No such thing

    >
    >How would I develop a class/set of classes for connection pooling
    >(no, I don't want to use MTS)?


    Good, because it'll be shag all use to you in any case!


    >Is there a way that a class can be instantiated and
    >have that particular instantiated class available to all apps/classes
    >that would like to use connection pooling?


    OK, I'm assuming you are talking about Database Connection Pooling,
    and not Object Pooling.
    If you want to do connection pooling, ADO should take care of it for
    you as long as all your apps use the same login details
    (i.e identical connection string)

    So, even if the apps use completely different instances of an object
    (or even different types of objects), your database connection will
    be shared as long as you use the same connection string.

    In short, use ADO, and you can open and close connections all day,
    and never think about pooling.

    Hope this helps.

    -Richard

  3. #3
    Kevin Downs Guest

    Re: connection pooling

    <Richard Dalton .> wrote in message news:3a889074$1@news.devx.com...
    > OK, I'm assuming you are talking about Database Connection Pooling,
    > and not Object Pooling.
    > If you want to do connection pooling, ADO should take care of it for
    > you as long as all your apps use the same login details
    > (i.e identical connection string)
    >
    > So, even if the apps use completely different instances of an object
    > (or even different types of objects), your database connection will
    > be shared as long as you use the same connection string.
    >
    > In short, use ADO, and you can open and close connections all day,
    > and never think about pooling.


    Oh come Richard, nothing is ever that simple....

    As I have said before; outside of COM+/MTS a connection pool only exists while
    there is at least one open connection. Once all connections are released, the
    pool is also released - so you are responsible for maintaining at least one
    connection at all times when you wish to use pooling.

    --
    Regards,
    Kevin



  4. #4
    Richard Dalton . Guest

    Re: connection pooling


    "Kevin Downs" <Kevin@optushome.com.au> wrote:
    >Oh come Richard, nothing is ever that simple....


    Granted, my mistake. I shall consider my knuckles
    rapped.

    -Richard



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center