On Sun, Oct 26, 2003 at 11:31:15AM -0500, Edward J. Huff wrote: > On Sun, 2003-10-26 at 08:21, Niklas Bergh wrote: > > > It can.. if you are using the QThreadFactory.. I don't think that > > YThreadFactory is succeptible to this. > > > > I've checked this. QThreadFactory permits the caller to create a > thread if there are none available. YThreadFactory always uses the > last created thread to create the next thread when none are available. > Since calling thread never creates new YThreads, priority of a YThread > is always the priority of the creator of the YThreadFactory object. > > Purely accidental that this bug was avoided, but then chance favors > a clean refactoring job. > > -- Ed Huff
YThreadFactory is not "a clean refactoring job". It's a totally new implementation using a completely different algorithm. The fix is simply to have QThreadFactory set the thread priority of created threads explicitly to normal. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
signature.asc
Description: Digital signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
