RSSCloud Vs. PubSubHubbub: Why The Fat Pings Win
techcrunch.com
RSSCloud Vs. PubSubHubbub: Why The Fat Pings Win
1–8 of 8 posts
Re: RSSCloud Vs. PubSubHubbub: Why The Fat Pings Win
#2The 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.
Re: RSSCloud Vs. PubSubHubbub: Why The Fat Pings Win
#3The submitted link forgot the 'l' in cloud. Here's the actual link: http://www.techcrunch.com/2009/09/09/rsscloud-vs-pubsubhubbu... 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.
Re: RSSCloud Vs. PubSubHubbub: Why The Fat Pings Win
#4Re: RSSCloud Vs. PubSubHubbub: Why The Fat Pings Win
#5The 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
Re: RSSCloud Vs. PubSubHubbub: Why The Fat Pings Win
#6Re: RSSCloud Vs. PubSubHubbub: Why The Fat Pings Win
#7Re: RSSCloud Vs. PubSubHubbub: Why The Fat Pings Win
#8 * PubBub for a publishing client;
* HubBub for a hub; and
* SubBub for a subscribing client.