Archive >  2009 >  December >  26 Previous / Next


Scripting News, the weblog started in 1997 that bootstrapped the blogging revolution.

Update on CloudPipe work Permanent link to this item in the archive.

A picture named ninja.gifAs I noted in a post on Wednesday, I'm using the holiday to build out the CloudPipe protocol that I explained in a post on December 9.

I'm getting pretty close to the point where I'll write docs and put it up for review.

But I wanted to post a heads-up now that I've made a change in how it works, a difference between the actual protocol and the December 9 narrative.

It says: "When the server detects a change in a feed the client is subscribed to, either through polling or notification, it sends a packet to the client indicating the feed has changed. The client then reads the feed, and processes it the same way it would if it had detected the change through polling."

The client may read the feed but I implemented and will specify a "fat ping." Along with the URL of the feed, we send the content of the item. If there are two items that changed, then two complete fat ping packets are sent. (This should answer in advance the question of how many items may be contained in a ping -- one and only one.)

I went this way for two reasons:

1. Competitive -- It's often mentioned as the reason people prefer PubSubHubBub over rssCloud. By providing for a fat ping, we erase that advantage. Now the two methods are at least at parity, with an edge to rssCloud because, once CloudPipe is done, it will work for clients that are behind firewalls and NAT, and PSHB does not.

2. Efficiency -- I learned when I met with the Tumblr guys in NY earlier this month that their feeds get pounded. The number one most referenced pages on their sites are the feeds. When I was running UserLand, it never was an issue, but we had a very small fraction of the traffic that Tumblr, WordPress, Blogger, Typepad etc have. Now that I know it is an issue, I want to address it. By sending the content along with the ping, in the realtime layer that's building now there will be fewer feed reads.

Now there's the question of whether to normalize the contents of an item. I can do it, but it might be a politically sensitive issue. Right now I have bigger fish to fry, so I won't normalize items, what you get in the fat ping is exactly what the feed broadcast. You'll have to deal with all the variability that can appear in the various flavors of RSS and Atom. I could make it so you didn't have to, but... We'll get to that later.

I expect to have a server for people to test against and docs for the protocol before January 1. Knock wood, praise Murphy, etc etc.

Update: Here's a 5-minute podcast that explains what these fat pings are all about.

A new Facebook API Permanent link to this item in the archive.

Christmas is over but we're still hoping for lots of goodies in a new API from Facebook. I explained over on the Realtime RSS blog yesterday.

Realtime RSS: Dear Santa: Please, a new Facebook API.

This is part tea-leave-reading and part pure conjecture, with a huge does of wishful thinking.

A picture named patrioticSanta.gif

Enjoy!

     

Last update: Saturday, December 26, 2009 at 6:30 PM Pacific.




~My Projects~

Droidie

Rebooting The News

ListBrowser.org

Protoblogger.com

My Father's Site

rssCloud

River2

Berkeley list on Twitter

The Bay Bridge Blog

Unberkeley blog


~About the Author~

A picture named dave.jpgDave Winer, 54, pioneered the development of weblogs, syndication (RSS), podcasting, outlining, and web content management software; former contributing editor at Wired Magazine, research fellow at Harvard Law School, entrepreneur, and investor in web media companies. A native New Yorker, he received a Master's in Computer Science from the University of Wisconsin, a Bachelor's in Mathematics from Tulane University and currently lives in Berkeley, California.

"The protoblogger." - NY Times.

"The father of modern-day content distribution." - PC World.

One of BusinessWeek's 25 Most Influential People on the Web.

"Helped popularize blogging, podcasting and RSS." - Time.

"The father of blogging and RSS." - BBC.

"RSS was born in 1997 out of the confluence of Dave Winer's 'Really Simple Syndication' technology, used to push out blog updates, and Netscape's 'Rich Site Summary', which allowed users to create custom Netscape home pages with regularly updated data flows." - Tim O'Reilly.

http://twitter.com/davewiner

Dave Winer Mailto icon

My most recent trivia on Twitter.

My Amazon.com Wish List

On This Day In: 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 1997.

December 2009
Sun
Mon
Tue
Wed
Thu
Fri
Sat
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
 
Nov   Jan



Click here to see an XML representation of the content of this weblog.



© Copyright 1997-2009 Dave Winer.


Previous / Next