Rob Bloodgood muttered:
> OK 1: none of the example environments you listed that your programmers are
> in include straight mod_perl... in fact they are all CGI emulation layers of
> varying degrees of protection/dirtiness. Do I read you correctly?
Yes, they're all CGI emulations.
> Well, this is all fine except for one important detail: HOW, and I mean, if
> you can't answer this you haven't solved the problem, but HOW do you know
> that your programmers' programs are going to fire a 503 if there is a
> database error????
> ...
> But the only way for this setup to work is if the PROGRAMMERS know that if a
> database call fails, to throw 503:
> ...
> Otherwise, all of this fancy footwork you're doing will be
> pointless.
You are correct, but I know, they'll fire a 503 because they all use a
DB class we provide in our API to connect to the DB (no one connects
'directly' using DBI). Since we've overridden DBI's connect method
with one of our own, we can fire a 503 when the DB connection fail.
Thanks again,
-Jim
--
<[EMAIL PROTECTED]> (Replace Z's with E's to reply)
"Camel's weren't designed to smell good. Neither was Perl."
-Larry Wall
PGP signature
