This issue was aired considerably in this thread:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/8665766f5e262d60
On Sep 7, 9:33 am, Monica Keller wrote:
> +1 definitely !
>
> I think everyone asks Twitter the same question but the problem was
> they developed the
+1 definitely !
I think everyone asks Twitter the same question but the problem was
they developed the firehose prior to PHSB
What are the main cons of PHSB ?
On Mon, Sep 7, 2009 at 8:48 AM, Jesse Stay wrote:
> Not necessarily. See this document (which I've posted earlier on this list)
> for d
One question is how does friendfeed handle protected updates since
the streaming api is for public statuses only ?
On Mon, Sep 7, 2009 at 6:32 AM, John Kalucki wrote:
>
> Friendfeed consumes the Twitter Streaming API to update Twitter
> status. SUP is not employed.
>
> All Twitter accounts have
Why would you use the db ? Just do it all in memory right ?
On Mon, Sep 7, 2009 at 6:52 AM, Dewald Pretorius wrote:
>
> SUP will not work for Twitter or any other service that deals with
> very large data sets.
>
> In essence, a Twitter SUP feed would be one JSON array of all the
> Twitter user
Not necessarily. See this document (which I've posted earlier on this list)
for details: http://code.google.com/p/pubsubhubbub/wiki/PublisherEfficiency
In essence, with PSHB (Pubsub Hubbub), Twitter would only have to retrieve
the latest data, add it to flat files on the server or a single column
SUP will not work for Twitter or any other service that deals with
very large data sets.
In essence, a Twitter SUP feed would be one JSON array of all the
Twitter users who have posted a status update in the past 60 seconds.
a) The SUP feed will consistently contain a few million array entries.
Friendfeed consumes the Twitter Streaming API to update Twitter
status. SUP is not employed.
All Twitter accounts have access to the Streaming API, documented
here: http://apiwiki.twitter.com/Streaming-API-Documentation
-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.
On Sep 7,
