Menu
I'm creating several RSS feeds from a database to publish things like job openings, volunteer opportunities, and links in general. My question is, how many items should be returned in the feed so that it is most likely that someone will get all the items in their reader without any gaps?
SELECT TOP 100 ? (obviously would need to be set for # of feeds estimated over X time)
SELECT the last 24, 48, 72 hours?
If I run my feed through Feedburner, does anyone know if they check on a certain interval so that I can create it to their standard and be assured that the Feedburner feed will contain all items?
700
RSS Feeds are an easy way to stay up to date with your favorite websites, such as blogs or online magazines. If a site offers an RSS feed, you get notified whenever a post goes up, and then you can read a summary or the whole post.
Since it's updated with details about every piece of content a site publishes, you can use RSS feeds for things like keeping up to date with every new article your favorite blog publishes or automatically generating email newsletters or social media posts to promote your new content.
It will look like waves, similar to a Wi-Fi icon. Click it and copy the URL. Finding RSS icons on the homepage of a website is less common than it used to be, so if you don't see it, you can perform a web search, such as "Insider RSS feed." Find the page and copy the link.
Well, it would depend on the rate that entries show up.
But I'd be guessing that aiming for the last 48 or so hours would be safe - seeing as a lot of users would be running stand alone RSS readers that will need to hit the feed to pull down whatever is current. But if that is going to be too much data, then maybe just limit it. 100 would be a lot though.
It would also depend on how the users would consume that data. Job openings would probably work with that volume, but users can get swamped if they're constantly seeing too many entries come in, and unsubscribe.
And you'll need to be wary of the size of the actual feed itself. Some feed aggregation services put a limit like 512kb and won't relay it if it gets bigger than that.
52
If you've done the hard work of creating the feeds in the fist place then offer querystring variables to affect what records are returned.
I did something similar recently for an intranet-based feed, like this
feed.asp?d=3&n=100
Which returns the last 3 days worth of feeds with a maximum of 100 records.
Similarly,
feed.asp?d=7 (all records for the past 7 days)
feed.asp?n=10 (the last 10 records)
Then users can adjust the feed to suit their circumstance as you typically can't possibly have one feed that caters for all users' requirements.
While this doesn't help you with your "default" values when feed.asp is requested, it does at least allow techy users to modify the feeds if they so wish. Make sure you check the querystring values too, to prevent silly/malicious requests.
27
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
