If I recall correctly, Jeffrey Baker (author of Apache::Session) wrote an extremely lucid and well thought out argument about why the way mod_perl pools connections is just as well as Java in reality.

Try searching for his name in the mod_perl list archives.. I think he wrote this over a year ago, but less than 2 years ago.

Later,
Gunther

Michael Teter wrote:
Howdy.

I'm very new to mod_perl, so if this question makes no sense, say so :)

My understanding is that database access via mod_perl is pooled, but only
per-httpd.  So if I had 10 active httpds running, I would have 10x(number of
connections per pool).

In contrast, my Java/JSP/Servlet solution has a single pool.  I'm trying to
evaluate mod_perl to use instead of my current Java-based solution, but the
potentially high number of database connections scares me.

Do production, public mod_perl-based sites have 10s or 100s of database
connections open?

Any direction will be appreciated.

Michael

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com





Reply via email to