I guess this post was a Christmas present from Dave. Happy Holidays
everyone!

On Dec 27, 2009 3:11 AM, "Pádraic Brady" <[email protected]> wrote:

I think what's happening is the inevitable. Over the past few months we've
seen PuSH rolled out, discussed, adopted, poked with a stick, etc. It's come
through unscathed. rssCloud outside of its Wordpress adoption hasn't gotten
the same attention or adoption. Those of us actually implementing these
things always had two issues - fat ping efficiency, Atom support and
unreliable security. PuSH has not had these as issues.

At every turn rssCloud is taking a long time to solve issues PuSH addressed
almost from the start. I mean, rssCloud still doesn't have formal Atom
support - Dave keeps mentioning Atom but he has never specified a namespace
to use for the rsscloud element - and there are now three possibilities: the
rssCloud URI, a third-party article suggestion, and the RSS Advisory Boards
proposed RSS 2.0 namespace. It's an implementation nightmare for Atom.

>From the article, Dave's remaining shots at PuSH are desktop client
communications. Presumably he hasn't heard of XMPP, Comet or long polling -
all of which can be applied with PuSH. Indeed, his own rssCloud solution is
nothing more than standard long polling. I can do that in my sleep with the
efficiency afforded by a light server such as nginx (and I'm sure the
Python/Ruby guys have their own language alternatives too).

This is all a good thing in a way. For those watching the news, it shows
PuSH got it right and rssCloud is only now catching up and backtailing on
previous statements.

  Pádraic Brady http://blog.astrumfutura.com
http://www.survivethedeepend.com OpenID Europe Founda...

------------------------------
*From:* Alan Williamson <[email protected]>
*To:* Pubsubhubbub <[email protected]>
*Sent:* Sun, December 27, 2009 8:35:37 AM
*Subject:* [pubsubhubbub] Re: rssCloud - it just keeps changing...

What i find most alarming about that article is Dave's line: "I learned when
I met with the Tumblr...

Reply via email to