http://bugs.gpodder.org/show_bug.cgi?id=173
--- Comment #8 from Tyler Rick <[email protected]> 2009-03-09 19:44:29 --- Here's another related problem that I found annoying (should I start a new bug for this?): I THINK part of the reason I was GETTING many of those errors (esp. "Connection reset by peer") in the first place was because gPodder was trying to download so many episodes AT ONCE causing the connection to be saturated and connectivity to suffer. Is that possible? I recently did a Check For Updates and after queuing all 575 new episodes, it started downloading ALL of these queued episodes simultaneously. I soon noticed the "Limit downloads to" option and enabled it, but by then it was too late, it seems. All downloads that it had already started processing (100s of them) CONTINUED to download despite my having limited it to 3 downloads at a time. (And then 30 or so error messages popped up over the course of 30 minutes, leading me to find this bug...:)) Perhaps a behavior similar to that described in Bug 19 would be more desirable: > All active and queued downloads will not be deleted when gPodder is closed, > and > gPodder will ask the user if she wants to continue downloading at next startup (if not, the partial files are deleted). So in my case all but 3 of the active downloads should be stopped immediately stopped and then resumed when it gets done with the first 3. Furthermore, I think that "Limit downloads" should be enabled by default so new users don't get this :) -- 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
