Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...

What is the difference between Connection Pool and data source?

Answer Posted / jaydeb chakraborty

Applications access a data source using a connection and
access Databases via DataSource objects.

A DataSource has a set of properties that identify and
describe the real world data source that it represents.
These properties include information such as the location
of the database server, the name of the database, the
network protocol to use to communicate with the server, and
so on.
DataSource object can be thought of as a factory for
connections to the particular data source that the
DataSource instance represents. In a basic DataSource
implementation, a call to the getConnection method returns
a connection object that is a physical connection to the
data source.

DataSource objects that implement connection pooling also
produce a connection to the particular data source that the
DataSource class represents. The connection object that the
getConnection method returns is a handle to a
PooledConnection object rather than being a physical
connection. An application uses the connection object in
the same way that it uses a connection. Connection pooling
has no effect on application code except that a pooled
connection, like all connections, should always be
explicitly closed. When an application closes a connection
that is pooled, the connection is returned to a pool of
reusable connections. The next time getConnection is
called, a handle to one of these pooled connections will be
returned if one is available. Because connection pooling
avoids creating a new physical connection every time one is
requested, it can help applications run significantly
faster.

Is This Answer Correct ?    14 Yes 2 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

What are the recommend parameters to improve the prformance from data-source point of view.

955


Explain what are the ways to avoid resourceexceptions when sending requests for databaseconnections?

931


What causes an ociw32.dll error? : BEA Weblogic

1116


Can you briefly describe local interfaces?

962


Can We Start A Managed Server If The Administration Server Is Unavailable ?

885


How do I restrict access to servlets and jsps? : BEA Weblogic

940


What does isidentical() method return in case of different type of beans?

913


Can weblogic server start with a unix boot? : BEA Weblogic

910


How to update license?

941


Explain the difference between dynamic and non-dynamic changes in the console?

1000


What is wlst?

953


What are the special design care that must be taken when you work with local interfaces?

904


How do clients handle dns requests to failed servers?

914


What is Multicast?

1013


How do I call oracle stored procedures that take no parameters? : BEA Weblogic

871