RE: Understanding/Defending Coldfusion connections

[Gaulin, Mark]

I suppose it could be useful for db connections to time out after a period of disuse, but I've never been in a situation where that would be truly useful... idle db connections don't take up many resources on a MS SQL Server, for example.  Again, I suppose it might come into play more for stand-alone apps (where there might be many instances running) vs. an app server (where you'd expect fewer instances, generally).


I have no idea if .net times out db connections... I'm just trying to find *some* reason why the argument might be slightly valid.  Clearly dropping and reconnecting to the db sucks for performance, so it can't be doing that...


    Mark


-----Original Message-----
From: Dave Watts [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 23, 2004 12:07 PM
To: CF-Talk
Subject: RE: Understanding/Defending Coldfusion connections

> "said cold fusion ****[is no good] because it keeps a
> database connection open all the time and that slows down the
> program/app and server"

Uh, it's much slower generally if you don't keep database connections open.
After all, your application is constantly using the database, and if you
have to destroy and recreate database connections every time you want to
talk to the database, that's a lot of unnecessary overhead.

However, if you don't want to maintain database connections in CF, there's a
handy checkbox for that within each datasource configuration page.

> This particular web professional is converting all his CF to
> dot net, because of this defense.

I would hesitate to use the word "professional" in this context.

Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
  _____

---

[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

---