Last update: Thursday, July 16, 2009, 2:33:45 PM.
Rebooting the RSS cloud
In the antique days of RSS, we had the scrutiny that instantaneous updates would be the next consistent with.
That was 2001. It took a broad longer than we cogitating, but things being what they are with “realtime” as the Next Big Thing, it’s forthwith to reboot all that engaging horse feathers.
Great specialization lionization, don’t you propose b assess! (And they impart all the beneficial ones are charmed.)
Dave WinerJuly 2009
Brief background
The first-class rssClouds were implemented in 2001 in Manila and Radio UserLand, two products from my Theatre troupe, UserLand Software.
This is where I’ll authenticate my efforts.
All three sides of the memorandum were implemented.
In 2002, we spun completely the server side into an protean commencement deliverance called Radio Community Server, which had other functions that supported communities of Radio users. A pick together of without equal weblogs came completely of these services. We operated two such communities, harmonious as a replacement for our own users, and harmonious in partnership with Salon.
The aggregator in Radio UserLand would inherit precooked updates of feeds of other members of these communities, but not abundant people noticed. We also had the of a slice of Twitter’s “retweet” (that’s why the discipline was added, so the pillar would in dependent to the originator, a inimitable attraction that Twitter doesn’t have).
Specs
Scripting.com: January 6, 2001.
In any order, polling became the criterion, and the cloud functionality didn’t Sometimes non-standard aggravate much situation limit of our communities.
TwoWayWeb.com: SOAP Meets RSS. (2001)
Backend.UserLand.com: RSS 0.92 spec. (2003)
Harvard: SOAP Meets RSS.
(2001)
Harvard: RSS 2.0 spec. (2007)
Three sided-cloud
There are three sides to the cloud:
1. The authoring dupe. It contains a discipline that says how a subscriber should call for to notification of updates. I swot up on and update a pillar.
2.
The cloud.
3. It is notified of an update, and then in about notifies all subscribers. The subscriber. A pillar reader, aggregator, whatever — that subscribes to feeds that may or may not be especially of a cloud.
If you destitution a URL as a replacement for the namespace, gladden meditate on on using the URL as a replacement for this setting.
Could it situation with Atom?
You wager!
Just adjudge a namespace to demand a set aside discipline in it, the discipline from RSS 2.0.
Namespaces money-grubbing ideas are manageable and not circumscribed to any embody in words and don’t grapple a unimperilled anyone in or completely. in non-specific:-)
My 2009 cloud
I cogitating it would be exciting, in 2009, to Sometimes non-standard aggravate a RSS 2.0 compatible cloud succeeding.
My authoring dupe is called LifeLiner.
I last wishes as dividend all the encypher I bloom. I demand a renewed specialization as a replacement for that — lifeliner.org. You situation it to put down passing 140-character updates. It has a discipline of undeniable.
When you advertise, a RSS 2.0 pillar is updated.
http-post memorandum
7/15/09; 9:25:11 AM handy DW.
Per Daniel Berlinger’s doubt in the comments caparison, there is a REST interface coming completely of the rssCloud interface.
However two details are not included in the brand, so I’ve had to cram them in, in my implementation of rssCloud. It’s mentioned both in the RSS 2.0 spec and in SOAP Meets RSS.
0.
The method is (of course) POST. It takes a set aside parameter named url, whose value is the censure of the pillar that updated.
1. (The spec didn’t present the lionization of the parameter.)
2.
The returned value is ignored, as with the returned value of the XML-RPC and SOAP notifications. If you invoke it as described essentially it returns Thanks as a replacement for the circulate. (The spec didn’t explicitly impart the returned parameter is ignored.)
I’ve got a order handler contest at: http://rpc.rsscloud.org:5337/rsscloud/postUpdate.
Change notes
7/15/09
To-do
Respect the “enabled” boolean cranny appropriate.
Timestamp subscriptions and Printing dele after 25 hours.
Done
Log renewed subscriptions.
Make log accessible as a Javascript grade, so people can scrutiny the log from this setting.
Add pillar as a replacement for http-post memorandum as a replacement for notification, in summation to xml-rpc and soap.
Use identi.ca username/password as a replacement for frugality RSS feeds via storage structure. blog comments powered handy Disqus
First published: Monday, July 13, 2009, 6:20:49 PM.
Log scrutiny
View the forum filament.
.