php5.handling errors. customers/user perspective
Posted: Mon Jul 03, 2006 10:47 am
Hi,
I am gathering some info about how should problems be served to users.
Question is design only..no code involved.
Say your application is database dependent (e.g mysql).
1. Do you consider sql query failure a fatal error?
2. Do you handle fatal errors and how do you present this to users?
3. Maybe what layers/architecture the apliaction consists of so that errors are handled in one place?
How do you generally approach these problems?
I gennerally try to handle every single point where an error might occur which is kind of wrong I thing.
First of all the application gets kind of ugly with all these checks and second of course at some point it is hard to mantain.
I am thinking maybe an observer pattern is good to implement so when an error occurse some object is filled with error info and stuff.
I am gathering some info about how should problems be served to users.
Question is design only..no code involved.
Say your application is database dependent (e.g mysql).
1. Do you consider sql query failure a fatal error?
2. Do you handle fatal errors and how do you present this to users?
3. Maybe what layers/architecture the apliaction consists of so that errors are handled in one place?
How do you generally approach these problems?
I gennerally try to handle every single point where an error might occur which is kind of wrong I thing.
First of all the application gets kind of ugly with all these checks and second of course at some point it is hard to mantain.
I am thinking maybe an observer pattern is good to implement so when an error occurse some object is filled with error info and stuff.