If you had ideas about the previously noted RSS Scaling Problem and are at OSCON now, stop by Douglas Fir to chat about it. Here's the session blurb:
With RSS usage growing like mad, does having every client pull their own copy still make sense? Might it make more sense for some centralized services to aggregate the data? Or maybe a push system? PubSub? Other ideas?
Let's toss some ideas around.
Or see the session page.
Posted by jzawodn at July 29, 2004 02:02 PM
Please post comments/ideas/etc. To bad someone can't run a IRC chat while it's going on. We have some ideas on how to handle but looking forward to more comments suggestions. As we our member base grows we have to handle not only the RSS load but the load on the website.
Thanks
Stuart
"Feed Your Need to Shop.."
Real Simple Shopping
www.realsimpleshopping.com
Adding a centralized hub just seems like solving the problem the usual way, just adding another layer of abstraction.
As others have pointed out, using techniques like HTTP Conditional Get and HTTP compression, server load can be dramatically reduced, today. Nothing new.
Oops, I see what I said was already mentioned in your previous post. Just to add then there needs to be an effort to make sure all the major clients support such things.
One thing I noticed that Mark Fletcher said was "the aggregator still has to query the server, so there will always be a load issue." Well duh, server are supposed to have a load on them. If the load is problematic, then there are already ways to solve this.
The scaling concern is simply exaggerated. Dare made Chad look dumb in raising the concern. Should I poll Yahoo! feeds 288 times per day?
I started to make a comment or two on what happened at the meeting, but turned into a very long comment. Thought it better to put thoughts on the meeting somewhere else.
RSS is OK as we don't get spammed. People have to use HTTP well, as previously stated.
My webpage is arhuaco in geocities... which is questionable content :)