Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Jeffrey Ryan Thalhammer
committed
Apr 21, 2012
1 parent
9364d30
commit d38d4f3
Showing
3 changed files
with
54 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
Exception strategy... | ||
|
||
All untrapped error messages need to go through the log so they get | ||
transmitted to the client | ||
|
||
Exceptions that originate from an Action do not require a stack trace. | ||
|
||
Exception that arise due to invalid user input do not require a stack | ||
trace. | ||
|
||
Exceptions that are not expected (db, network, file system) do require | ||
a stack trace. | ||
|
||
If the log level is debug, then all errors should be recorded with a | ||
stack trace. | ||
|
||
Data validation strategy... | ||
|
||
Actions should validate as much as possible during construction. | ||
|
||
The Repository should validate arguments. | ||
|
||
The Database & collaborators may not validate arguments. | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
Logging strategy... | ||
|
||
Actions emits one log message at 'notice' level that describes | ||
the overally goal of the action. | ||
|
||
Repository emits one or two log messages at 'info' level for each major | ||
operation. Minor operations logged at 'debug' level. | ||
|
||
Database, cache, & collaborators always log at 'debug' level. | ||
|
||
#---------- | ||
|
||
What is the purpose of the log??? | ||
|
||
* To record who made what modifications to the repository and when | ||
|
||
* To help debug and diagnose operational problems | ||
|
||
* To record operational events |