|
|
Log4Ajax
|
12/31/2005, By Eric Spiegelberg
|
An additional reason writing AJAX applications can be difficult is the lack of tools that are considered standard for server-side development, including a logging system. "Logging equips the developer with detailed context," according to the website for the popular Java logging framework Log4j. Because your AJAX application executes on the client machine and you have no detailed context of its state, how do you know when an error occurs? How do you know what events and application defects lead to the error? Thorough testing before a release increases your confidence in the product, but you can't prove a negative; just because bugs are not reported does not mean your end users are not experiencing them. Through logging, you have enough detailed context that you can be confident your application is not experiencing errors and is running smoothly.
Before diving into the details of Log4Ajax, this article assumes the reader has some level of familiarity with AJAX and DHTML. If not, the Web contains a wealth of information that would be redundant to duplicate here. Links to several good sources, including Joshua Gitlin's "Errors and AJAX," are included in the Resources section.
 Read more...
|
Rate this Ajax Articles
Rating: 0.0 out of votes cast
| |
|
|
|
|
|
|
|
|
|
|
|
|
Special offer for AjaxImpact.com Visitors!!
Subscribe to Oracle Magazine for Free!
