On 2002.10.18, Jim Wilcoxson <[EMAIL PROTECTED]> wrote: > > What is the point of having the DB module load, if it can't connect to > the DB server?
While I personally agree with you, the point (I think) that Pete is making is that for DB modules, this behavior should be up to the admin's control. If the DB driver loads successfully, but the database is unavailable, one should be able to trap it. If you want to validate that the database is available at start-up, you /should/ be allowed to do a ns_db gethandle from nsd.tcl to try and connect and ns_exit on failure, if you DESIRE that behavior. But to kill the whole server at runtime because the DB's inaccessible leaves no choice to website developers, which is a design flaw. My position: ANY module that fails to load should cause a hard fatal at start-up. There are very few, if any, reasons for a module to deliver a hard fatal to a system at runtime though. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70)
