TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

RSSCloud Vs. PubSubHubbub: Why The Fat Pings Win

23 pointsby curioover 15 years ago

5 comments

TomOfTTBover 15 years ago
The submitted link forgot the 'l' in cloud. Here's the actual link: <a href="http://www.techcrunch.com/2009/09/09/rsscloud-vs-pubsubhubbub-why-the-fat-pings-win/" rel="nofollow">http://www.techcrunch.com/2009/09/09/rsscloud-vs-pubsubhubbu...</a><p>The article itself is worth a read. The only thing that bugs me is that the author, and a lot of other people covering this story, don't mention that RSSCloud doesn't support Atom at all (or more accurately it does in theory but not in practice). I think that's pretty significant.
评论 #814811 未加载
alexandrosover 15 years ago
The article mentions that the explicit unsubscription of PuSH is an advantage over the implicit approach of rssCloud. With garbage collection being a major problem of publish/subscribe in distributed systems, the author needs to mention how PuSH deals with it in order to assert superiority. Without acknowledging it, the credibility of the article is limited
评论 #815188 未加载
juvennover 15 years ago
The coining word PuSH of PubSubHubBub is just ... marvelous
juvennover 15 years ago
That Bub part of PuSH seems as random bits. But I have got it used in:<p><pre><code> * PubBub for a publishing client; * HubBub for a hub; and * SubBub for a subscribing client.</code></pre>
msalvagnaover 15 years ago
I should think the reduced latency from receiving the data within the update would be a greater benefit of a fat ping.