Three sided-cloud

There are three sides to the cloud:

1. The authoring tool. I edit and update a feed. It contains a <cloud> element that says how a subscriber requests notification of updates.

2. The cloud. It is notified of an update by the authoring tool, and then in turn notifies all subscribers.

3. An aggregator. Subscribes to feeds that may or may not be part of a cloud.

What they call real-time 

via http://dashes.com/anil/2009/07/the-pushbutton-web-realtime-becomes-real.html via http://dashes.com/anil/2009/08/what-works-the-web-way-vs-the-wave-way.html

There are actually 3 protocols and 2 APIs that are used in Wave:

• Federation (XMPP)
• The robot protocol (JSONRPC)
• The gadget API (OpenSocial)
• The wave embed API (Javascript)
• The client-server protocol (As defined by GWT)

The last one in that list is really nothing that needs to be, or will probably ever be documented, it is generated by GWT and when you build your own Wave client you will need to define how it talks to your Wave server. The rest of the protocols and APIs are based on existing technologies.

"The core argument behind the presentation can be summarized by this tweet from Tim O'Reilly On monday friendfeed polled flickr nearly 3 million times for 45000 users, only 6K of whom were logged in. Architectural mismatch. #oscon08 On July 21st, FriendFeed had 45,000 users who had associated their Flickr profiles with their FriendFeed account. FriendFeed polls Flickr about once every 20 – 30 minutes to see if the user has uploaded new pictures. However only about 6,000 of those users logged into Flickr that day, let alone uploaded pictures. Thus there were literally millions of HTTP requests made by FriendFeed that were totally unnecessary. Evan and Kellan's talk suggests that instead of Flickr getting almost 3 million requests from FriendFeed, it would be a more efficient model for FriendFeed to tell Flickr which users they are interested in and then listen for updates from Flickr when they upload photos. They are right. The interaction between Flickr and FriendFeed should actually be a publish-subscribe relationship instead of a polling relationship. Polling is a good idea for RSS/Atom for a few reasons"

"Welcome to JWChat at jwchat.org A web based Jabber/XMPP client"

"To communicate with Twitter we can use this cool Ruby Twitter API. Unfortunately ... So we need to interface with their Jabber Service. Jabber: name for IM using XMPP protocol. Luckily, there is a Ruby library called XMPP4R which does most of the XMPP work for us. This blog post provides some simple examples and this German wiki entry provides sample code how to use callbacks (very important for a bot)."