keryx team mailing list archive

Thread
Date

Re: Where should we do threading?

To: keryx@xxxxxxxxxxxxxxxxxxx
From: Douglass Clem <crashsystems@xxxxxxxxx>
Date: Mon, 6 Jul 2009 16:28:49 -0400 (EDT)
In-reply-to: <fwqsp3lddabpz544xsUYAxe124vaj_firegpg@mail.gmail.com>

I was just talking to Michael (mhall119) on IRC about threading, and he expressed some concerns regarding the potential for added complexity in putting threading in libkeryx. During the conversation, I came up with an idea for a compromise: write a class in a separate file, threading.py, which would handle threading. Any library/UI that wants to use threading could call it, but it's use would remain optional. What does everyone think of this?
-
Douglass Clem
Chief Technology Officer,
Crashsystems LLC (crashsystems.net)
Public Key: 37F9 E685 576A CFD3 B08C

Attachment: signature.asc
Description: OpenPGP digital signature

References

Where should we do threading?
From: crashsystems, 2009-07-04