So far, there have been three general implementation scenarios discussed on the Activity Streams email list. For each of these scenarios, there is a "publisher" of Activity Streams data and a "consumer" of Activity Streams data.
With each scenario description below is a listing of implementors. If you want to list another implementor, please follow the instructions on the process pwiki page.
In this scenario, the publisher emits a feed in ActivityStreams format and the consumer reads the feed (sometimes called "polling").
A "conversation" in this scenario might look like:
Consumer: What activities has John done on your site?
Publisher: John posted status today and posted photos yesterday (data is in Activity Streams format)
| Publishers (alpha, linked* to ASms wiki page) | Consumers (alpha, linked* to ASms wiki page) |
|---|---|
|
Adobe Wave AOL Livestream Collecta Digsby Gnip -- In Progress Google - Real Time Status Updates Groovy Corp People Browsr Topsy -- In Progress Yahoo Front Page |
End-to-end implementations:
| Publisher (linked* to ASms wiki page) | Consumer (linked* to ASms wiki page) | End-to-end Implementation |
|---|---|---|
| Cliqset | Community Equity | Community Equity site connect |
| Community Equity | Community Equity site connect | |
| Windows Live | Facebook web activity on Windows Live | |
| MySpace | TweetDeck | TweetDeck desktop client |
| MySpace | Windows Live | MySpace web activity on Windows Live |
| MySpace | AOL Livestream | In progress: http://lifestream.aim.com/settings |
| MySpace | Digsby | http://www.digsby.com |
| MySpace | Adobe Wave | http://labs.adobe.com/technologies/wave/ |
| MySpace | Collecta | http://myspace.collecta.com |
| MySoacew | Gnip | In progress |
| MySpace | Groovy Corp | http://www.groovycorp.com/index.php?option=com_content&task=view&id=8&Itemid=9 |
| MySpace | Google Real Time | In progress |
| MySpace | People Browsr | In progress |
| MySpace | Topsy | In progress |
| MySpace | Yahoo Front Page | http://m.www.yahoo.com |
In this scenario, a publisher pushes Activity Streams data to a consumer and the consumer recieves the data:
A "conversation" in this scenario might look like:
Publisher: John posted a new blog entry (data is in Activity Streams format)
Consumer: Got it, thanks. (The consumer might just reply with an affirmative response or might reply with how it understands the data (in Activity Streams format) )
| Publishers (alpha, linked* to ASms wiki page) | Consumers (alpha, linked* to ASms wiki page) |
|---|---|
|
|
|
In this scenario, a publisher emits a stream of data in ActivityStreams format and a consumer reads this via a persistent connection. In some cases, the consumer may periodically call back to the publisher to adjust subscription parameters for the stream.
A "conversation" in this scenario might look like:
Consumer: Tell me about all public activities on your service for users near Chicago, IL, USA
Publisher: John posted a blog entry at 9:57am (in Activity Streams format)
Publisher: Martha shared a video at 9:58am (In Activity streams format)
Publisher: John posted a bookmark at 10:00am (In Activity Streams format)
...
| Publishers (alpha, linked* to ASms wiki page) | Consumers (alpha, linked* to ASms wiki page) |
|---|---|
|
|
* Links are to the "<service-name>-Activity-Streams" wiki pages on http://wiki.ActivityStrea.ms . Please maintain this consistency.