refactoring: simplify the semaphorewait logic
The semaphorewait()/waitforthread() logic is usefull for IMAP starting connections. We actually use it in imapserver only. This patch removes the over-engineered factorized methods. It tend to simplify the code by cleaning out a chain of two direct calls with no other processes. Reviewed-by: Sebastian Spaeth <Sebastian@SSpaeth.de> Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
This commit is contained in:
@@ -300,7 +300,8 @@ class IMAPServer:
|
||||
to copy messages, then have them all wait for 3 available connections.
|
||||
It's OK if we have maxconnections + 1 or 2 threads, which is what
|
||||
this will help us do."""
|
||||
threadutil.semaphorewait(self.semaphore)
|
||||
self.semaphore.acquire()
|
||||
self.semaphore.release()
|
||||
|
||||
def close(self):
|
||||
# Make sure I own all the semaphores. Let the threads finish
|
||||
|
Reference in New Issue
Block a user