Finding myself on a host where I couldn't use NNTP to retrieve CPAN uploads from perl.cpan.testers, I decided to use POE::Component::RSSAggregator to do the job for me.
The resultant code is here
I'm polling every 1800 seconds, but you may care to adjust that
Happy smoking!
120 seconds?! That’s… well let’s benevolently call it “very eager.” Much like a young puppy who’s so happy he’s slobbering all over your face.
To be frank, that is not a friendly polling interval. Hopefully, the module you’re using implements Conditional GET so you’re not treading on the poor server’s bandwidth too badly, but 120 seconds is still rather obnoxious, if only because you flood the server’s logs with noise. You should have a really good reason to poll more frequently than every 10 minutes. In general, you should poll no more than once an hour. My own desktop aggregator is set to check feeds 4× per day, and for almost all of them that is plenty and them some.
Seriously, don’t be an information superhighway rowdy.
Re:RSS polling ettiquette
BinGOs on 2006-10-04T10:06:25
Suitably chastised, BinGOs wandered into the desert to thrash himself with silver birch
Seriously, I was going to up the polling period anyways, as it is delaying the execution of the tests of uploaded modules for 400000 seconds.
I'll raise it to once an hour and see how it plays out on server load
Re:RSS polling ettiquette
Aristotle on 2006-10-04T10:51:46
No need for flagellation, self- or otherwise. Just fix the code.
:-) I have committed my share of clueless transgressions. Within reasonable limits they aren’t an issue, so long as you clean up your act once you know better. (Why specs matter makes the relevant point quite eloquently, though mixed in with a bunch of other issues that aren’t directly relatable to the issue at hand.)
