On 2002.10.18, Peter M. Jansson <[EMAIL PROTECTED]> wrote: > One of the reasons I raised this point is that, today, modules are wildly > inconsistent about fataling. If the nssock module fails to load or to > listen, the server continues, ever hopeful; if the nscp module fails, on > the other hand, it's going down and it's not going alone!
I'd call this a defect in the nssock module. > As for database drivers, I think it's never acceptable for a driver to > fatal because of a failed connection -- [...] Can you please name names here? I maintain nsmysql and nsfreetds, do either of these do what you describe? I think if the module /itself/ fails to load, it should be a hard fatal error. If the module loads but a specific database connection can't be made, then you're right, it shouldn't take out the server. If either of my database drivers have this behavior, I'll agree that it's also a defect and will be fixed. -- 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)
