In article
<01577eab-d3de-4441-8622-2efdc2e3b8c3@[EMAIL PROTECTED]
>,
Taras_96 <taras.di@[EMAIL PROTECTED]
> wrote:
>On Apr 23, 10:41 pm, "joeNOS...@[EMAIL PROTECTED]
" <joe.weinst...@[EMAIL PROTECTED]
>
>wrote:
>
>>
>> The process of making a new connection is slow. It requires opening
>> a new socket from the client to the DBMS, which may require the DBMS
>> to spawn a new process, sending connection credentials, which the
>> DBMS must verify and respond to before any real work can be done.
>> A restaurant would be much less practical if it hired a waitress for
>> every new customer and terminated her when she finishes collecting
>> the bill.
>>
>> Joe Weinstein at BEA Systems
>
>So the cost saving is in the setup of a database connection, which
>includes opening a communication path between the two components
>(possibly using sockets), and authentication (although I guess that
>whatever is trying to acquire the database connection would still have
>to be authenticated)?
That's pretty much it. Creating the connection involves all that, and is
an
expensive operation. The connection pool manager acquires the connection
and
is authenticated, not the consumer of the connection. That authentication
is
only done once.
Eric
|
