RE: DorothyLocker and Tool diff

One caveat I forgot to mention: DorothyLocker *is* complicated stuff, and
*might* induce more errors than it's worth. Georg, you might want to make it
optional rather than inbuilt. 

-----Original Message-----
From: Garth T Kidd [mailto:garth-OnzZ1s1DREKDegMON/[email protected]] 
Sent: Thursday, 15 July 2004 5:45 PM
To: 'pyds-dev-iYtK5bfT9M//Ad8WF/[email protected]'
Subject: DorothyLocker and Tool diff

I've renamed NoisyLocker to DorothyLocker because of its insistence that
there's no place like home (i.e. the calling frame :). I've also
incorporated LockWhiner into DorothyLocker so Tool doesn't have to do any
tracking -- it can just call acquire() and release() and catch the
exceptions. With that bit of infrastructure, it should now be pretty easy to
figure out if someone's code is somehow screwing up on the locking. 

Once I suck all my posts from Radio to PyDS, I'll publish DorothyLocker in
its own right; I quite like being told when things are breaking, and will
use the code anywhere else I tackle threads. It also strikes me that it'd be
trivial to hack some kind of timeout into acquire -- something I'll leave
for much later, if ever. :) 

Regards,
Garth.