> -----Original Message-----
> From: Rob Bloodgood [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 02, 2001 9:18 PM
> To: Geoffrey Young
> Cc: mod_perl
> Subject: RE: Apache::DBI in startup.pl generating error
> > basically, it's a bad programming practice not to use()
> modules in the
> code
> > that needs them. it works if you call PerlModule before
> you use() the
> > module, but again, it requires you to pay better attention to your
> > httpd.conf than you ought to.
>
> See my above point. Apache::DBI is *made* to be transparent,
> or at least
> semi-. It exists at the server level, and without (much)
> interaction with
> the programmer's dataspace at all. What better place for it than
> httpd.conf? And as for having to pay too much attention...
> well... let's
> just say that RedCode is spreading like it is because not
> enough IIS Admins
> "paid better attention" to the defaults THEY were given. :-)
> Seriously tho,
> why WOULDN'T you know what exactly is in your server configuration?
well, I was going to leave this thread alone now, but I feel the need to
justify myself on this one issue - I wrote that email a bit bleery-eyed...
of course you need to know what your config contains. what I meant was that
relying on the PerlModule syntax to allow you to call
Apache::DBI->connect_on_init from your startup.pl was less than solid coding
- it's the same as not use()ing modules from the scripts that require them
(you didn't get that thought from what I wrote? I can't imagine why ;). as
for the rest of Apache::DBI you're right, it's transparent so it doesn't
matter where you load it - as long as you understand the
action-at-a-distance concept, and are comfortable with it, you're ok...
anyway, nuff said. Gunther and Ken tied things up nicely.
--Geoff
