-> > Is this overkill?  It allows sites to have different error handling for
-> > different parts of the site.  Would anyone actually use it?  Perhaps
-> > only allowing _q_exception_handler in the root namespace would be good
-> > enough.
->
-> It probably would be good enough most of the time.  But then *somebody*
-> will want to do something different and end up digging through the request
-> object to try to figure out where the exception actually happened.  I think
-> it's better to have it work as you described - drop in a handler anywhere
-> in the traversal path.  When I get around to handling errors gracefully,
-> I'll probably use it :)

I second that ;).

This mechanism would allow redirects after exceptions, correct?
I'd like to be able to raise an authorization exception & force
login from within different hierarchies, myself.

--titus