--- On Tue, 11/4/08, Christoph Zwerschke [EMAIL PROTECTED] wrote:
From: Christoph Zwerschke [EMAIL PROTECTED]
Subject: Re: [Webware-discuss] MiddleKit Threading Error?
To: Discussion of Webware for Python including feedback and proposals.
webware-discuss@lists.sourceforge.net
Date: Tuesday
Roger Haase schrieb:
I have downloaded the latest version of MiddleObject.py and verified
that putting the lock on the class level works for me. Per your
previous messages, it looks like you have already processed the 3
other MiddleKit changes in the queue.
Good to hear. Yes, I wanted to
Christoph Zwerschke schrieb:
Btw, I was trying to run the MiddleKit test suite, but I get many
errors. For instance when running python Test.py MKDelete I get a
Lock wait timeout exceeded (this hasn't anything to do with the lock
in the patch, I get it also without your patch).
I had
--- On Sun, 11/2/08, Christoph Zwerschke [EMAIL PROTECTED] wrote:
From: Christoph Zwerschke [EMAIL PROTECTED]
Subject: Re: [Webware-discuss] MiddleKit Threading Error?
To: [EMAIL PROTECTED], Discussion of Webware for Python including feedback
and proposals. webware-discuss
Roger Haase schrieb:
I had to revise your new MiddleObject.py to put the _mk_cacheLock =
threading.RLock() statement at the module level rather than in the
MiddleObject __init__ method. A new MiddleObject instance is being
created with each request so putting the lock inside the object
Roger Haase schrieb:
My revised solution is to put the lock at the beginning and end of the method.
I never used MiddleKit, so I don't know how to test this, but since it
looks reasonable I've checked this in anyway, and cleaned up
MiddleObject.py a bit. Can you check whether this works for
--- On Sun, 10/19/08, Roger Haase [EMAIL PROTECTED] wrote:
From: Roger Haase [EMAIL PROTECTED]
Subject: MiddleKit Threading Error?
To: webware-discuss@lists.sourceforge.net
Date: Sunday, October 19, 2008, 3:46 PM
I last reported this problem back on May 22, 2004. I am not
sure what I
I last reported this problem back on May 22, 2004. I am not sure what I have
been doing different lately, but I have encountered the problem on both my test
system and my production system this past month. I have never been able to
reproduce this problem at will. The problem last went away
