Hacker News Reader

Comment by stanleydrew | Hacker News Reader

Many many fewer HTTP requests.

I suppose webapps such as google reader query only once the source for all the users subscribed to a certain feed, effectively reducing the number of HTTP requests on the upstream provider. Isn't it a simpler and well tested solution to this problem? It basically makes the google server the Hub and your browser the subscriber to use the website's terminology.

You might say that Pubsubhubhub is the logical extension of the Google Reader concept. It allows you to "read" those feeds programmatically and enables the content site to notify Google Reader of updates so they get there quicker.

Also, anyone can choose to be a hub, not just Google Reader. There's your simple and well tested solution wrapped in a standard for anyone to implement.

It's converting a two-tier one-to-many pull system with 5 minute polling to a three-tier one-to-many-to-many push (err.. PuSH) system. More efficient, allows for quicker dissemination of update notifications.

Although comparatively more concurrent connections. The 'hub' looks somewhat like an IRC server. In fact, you can emulate this behavior with IRC.

That's not actually the case. It's one ping per event. You don't keep the connection open.

OK, the client must send periodic pings to the hub in order to receive updates.

Sheesh, did you bother to read the linked document?

The "client" in pubsub registers a call-back URL with the server, and the server then POSTs new data to that URL.

No periodic polling required -- that's the whole point of this.

Sorry, I was confused. I thought 'hubbub' was a drop-in replacement for RSS. Apparently, it's a meta-protocol built around RSS.

Reply on news.ycombinator.com