On Fri, Feb 20, 2009 at 4:05 PM, Jochen Schmidt jsc@crispylogics.com wrote:
Taking Hans suggestion I actually started a little section on error handling for the documentation. I can understand if you want it to do for yourself - but perhaps you're interested in what I've got so far. Drop me a mail if you do.
Thanks. Please send what you have and I'll see to incorporate it into the documentation. (Or it might be obsolete due to the next release. I'm afraid I'm not completely sure about what will be in there and how it'll look.)
One thing that Hans just mentioned in private conversation and which I think is quite important: Users of Hunchentoot should not be encouraged to write around methods for existing methods because that means to rely on the fact that these methods currently don't have an around method and won't have one in the future. (There might even be places in the documentation where I wasn't too clear about that.) The recommended way is always to subclass and then to write your own primary methods (which eventually call call-next-method) and/or to write around methods specializing on your own classes.