Getting the Message, Part 1
October 14, 2009 Paul Tuohy
When we look at modernizing (or writing new) applications, one of the basic principles is to tier the application, i.e., separate the interface, the business logic, and the database processing. The concept is that any of the components can be changed without affecting the others and, more importantly, you can have multiple interfaces making use of the same business logic and database routines.
That’s all well and good, but there are a couple of minor hiccups that have to be handled. What happens when a business logic or database routine hits an error? How does it notify the interface that