http://bugs.gpodder.org/show_bug.cgi?id=226
--- Comment #4 from Thomas Perl <[EMAIL PROTECTED]> 2008-10-21 12:38:04 --- Yep, seen that way that would probably be more intelligent than just starting a thread and letting it wait. The disadvantage would be that there would be several worker threads sitting around idle when no download is running, except if we go and change it so that threads are created and destroyed on demand. Which would probably be the current solution with a "work list" that will be added to in case all slots are full and after a thread has finished downloading one episodes, it checks this "work list" and maybe takes the topmost item from it and downloads this. When a thread finishes a download and the work list is empty, it simply quits. -- Configure bugmail: http://bugs.gpodder.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. _______________________________________________ gPodder-Bugs mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-bugs
