http://bugs.gpodder.org/show_bug.cgi?id=364
Summary: Implement aggresive timeouts for feed updates
Product: gPodder
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: low
Component: Application
AssignedTo: [email protected]
ReportedBy: [email protected]
When you have a lot of feeds subscribed, it might happen from time to time that
one of the servers you download the feed updates from doesn't respond. That's a
normal thing in the internet and nothing to worry about.
Unfortunately gPodder reacts a bit confused about those server timeouts: Using
the neat threaded feed updater, it happily and quickly downloads almost all
feeds and then suddenly stops one before the finish, showing something like
"Updated 35/36" and doing nothing else anymore. Even clicking the cancel button
usually doesn't bring gPodder back to live, usually I end up killing gPodder
completely to try my luck again.
What would be nice is a really aggresive timeout during the feed update: every
server that doesn't respond within 5 seconds will simply be skipped during this
turn, I usually don't care it a podcast just downloads a day later when the
server reponds faster again. Maybe the timeout should default to something like
30 seconds (so that people with slow connections don't suffer), but should be
able to be changed (in the "Advanced Preferences" would be enough).
And since the feeds already get marked bold, red and green sometimes, the
skipped feeds could just be marked yellow. ;)
--
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
