On Thu, 29 Apr 2004, Tatsuo Ishii wrote:
Depending on your web development environment (java, php, .NET) etc,
you should be able to use some mechanism that will provide a pool of
connections to the database. Each request does not open a new
connection (and then release it), but
Hello,
Depending on your web development environment (java, php, .NET) etc,
you should be able to use some mechanism that will provide a pool of
connections to the database. Each request does not open a new
connection (and then release it), but insteads gets a connection from
the pool to
On Wed, 2004-04-28 at 17:58, Chris Browne wrote:
[EMAIL PROTECTED] (Kilmer C. de Souza) writes:
Oww ... sorry man ...
I make a mistake ... there are 10.000 users and 1.000 from 10.000 try to
access at the same time the database.
Can you help me again with this condition?
Stefan Sturm wrote:
Hello,
Depending on your web development environment (java, php, .NET) etc,
you should be able to use some mechanism that will provide a pool of
connections to the database. Each request does not open a new
connection (and then release it), but insteads gets a connection
Depending on your web development environment (java, php, .NET) etc,
you should be able to use some mechanism that will provide a pool of
connections to the database. Each request does not open a new
connection (and then release it), but insteads gets a connection from
the pool to
Bill Moran wrote:
Stefan Sturm wrote:
Hello,
Depending on your web development environment (java, php,
.NET) etc, you should be able to use some mechanism that will
provide a pool of connections to the database. Each request
does not open a new connection (and then release it), but
insteads gets a
On Thu, 29 Apr 2004, Tatsuo Ishii wrote:
Depending on your web development environment (java, php, .NET) etc,
you should be able to use some mechanism that will provide a pool of
connections to the database. Each request does not open a new
connection (and then release it), but
