Tom Samplonius wrote:
> On Sun, 26 Nov 2000, Alain Toussaint wrote:
> > > "I have all sorts of client apps, connecting in different ways, to
> > > my server. Some of the clients are leaving their connections open,
> > > but unused. How can I prevent running out of backends, and boot
> > > the inactive users off?"
> > how about having a middle man between apache (or aolserver or any other
> > clients...) and PosgreSQL ??
> I don't see it solving anything. You just move the connection
> management problem from the database to the middleman (in the industry
> such a thing would be called a query multiplexor). Multiplexors have
> often been used in the past to solve this problem, because the database
> could not be extended or protected.
And I'm requesting protection. Because the database isn't capable of dynamically
detroying temporary backends. (Which would be another solution to this
problem)
> Besides, if you are an n-tier developer, this isn't a problem as your
> middle tier not does connection management, but some logic as well. At
> the end of the day, PHP/Apache is just not suitable for complex
> applications.
Is it dump on PHP day?
Okay, pretend the problem is left-open Perl connections. Slam that for
a while. Move over to left open Access connections. Bag on that for
a few posts. Errant C code for a few days. Still have a problem. :-)
How does a db admin close connections that are idle, and unwanted, without
shutting the postmaster down?
-Bop
--
Brought to you from iBop the iMac, a MacOS, Win95, Win98, LinuxPPC machine,
which is currently in MacOS land. Your bopping may vary.
