alvaro at octality
Sep 2, 2009, 7:39 AM
Post #1 of 1
(222 views)
Permalink
|
|
New error reporting mechanism
|
|
Hello there,
I just wanted to let you know that I've created a new repository
branch to work on a new error reporting mechanism. The target is
to report more comprehensive error messages, and try to do the in
the most friendly way:
svn://cherokee-project.com/cherokee/branches/newerrors
The new mechanism is not rocket science, although it isn't something
trivial to integrate either. Besides, it requires to modify each
single LOG_*() reference along the code, so it's prone to introduce
regressions. We'll have to be extremely careful when working on this.
Some notes about the new mechanism:
- Errors are not longer spread along the code. All of them are
located in cherokee/error_list.py now.
- 'make' will generate a couple of files with the C representation of
the code. BTW, It's a fairly smart script; it should warn about most
of the potential problems.
- The new mechanism report much more information than the previous
(current), including: title of the error, an extended description of
the issue, an optional URL to cherokee-admin, the current time,
server version, backtrace (if enabled), etc.
TODO:
- Update Cherokee-admin, so it reports these extended errors nicely.
- Replace all the old LOG_* calls.
Check these files to see the new format:
- Error definition file:
http://svn.cherokee-project.com/browser/cherokee/branches/newerrors/cherokee/error_list.py
- A source file already converted to use the new LOG_* format:
http://svn.cherokee-project.com/browser/cherokee/branches/newerrors/cherokee/buffer.c
Comments are welcome!
--
Octality
http://www.octality.com/
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev
|
