On Saturday 07 June 2003 5:56 pm, Jason Sibre wrote:
> Mark,

Hi Jason,

> The idea is this:  When doing _q_lookup, I make sure they are
> logged in, and if not, raise my sub-class of AccessError.  As a
> sub-class of PublishError, this is caught by the quixote machinery,
> which in turn checks to see if I have an exception handler in place
> which will handle it.  I do, and it handles it by redirecting to
> the login screen.

Nicely done.  Works for me.

> One thing to note along these lines...  the _q_exception_handler
> thus called must be in the root namespace of your app.  It cannot
> be in a sub-module, or in an previously _q_lookup-ed object, as
> those are not yet part of the namespace stack at the time a
> Traversal-time exception is being handled. I've submitted a patch
> to remedy that, but I haven't gotten a reply on it, yet.  Either
> the Quixote's maintainers are busy, or missed it, or they didn't
> like it ;)

Too busy, I'll bet.  Perhaps resend with a subject line that includes
[PATCH].  If we all follow that convention, it should be a bit easier
for the mems folks to find the patches.

> I've attached snippets of my code below to demontrate.  (I've
> hacked this up a bit to eliminate some code that I didn't think
> pertained, so it may not look completely sensible, and may not even
> run as you see it, but it should make my intent clear.)

I found this code interesting to read, thanks.  app = getApp().  Hmmm
...  :)

> Hope this helps,

Yes, indeed.  Thanks!

> Jason Sibre

Regards,

Mark