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 capabilities of weblogic server?

1067


What are logics in reference to web logic servers?

897


What is Unicast?

963


What happens when a failure occurs and the stub cannot connect to a weblogic server instance? : BEA Weblogic

1019


How to integrate sunone/netscape/iplanet with weblogic?

931


You are noticing a performance impact on your application and you suspect the underlying operating systemresources might be causing the issue, what steps would you take to narrow down the issue?

981


What are class paths?

984


What are the ways in which weblogic servers can run on multiple machines?

971


Difference between weblogic development and production mode?

965


How do I use os authentication with weblogic jdriver for oracle and connection pools? : BEA Weblogic

941


Is it possible to set aside a message and acknowledge it later? : BEA Weblogic

884


Tell me how are the notifications generated when a server is added to a cluster?

948


Explain weblogic server?

957


Explain about cluster heart beats?

947


How do I get a thread dump to help track down a problem? : BEA Weblogic

888