Twitter's problems are the result of architecture, XMPP may be the answer(slashstar.com)
slashstar.com
Twitter's problems are the result of architecture, XMPP may be the answer
http://slashstar.com/blogs/tim/archive/2008/05/05/twitter-s-problems-are-the-result-of-architecture-xmpp-may-be-the-answer.aspx
2 comments
I'm not familiar with Tweetscan's specific implementation, but I would assume they're just grabbing the public XML feed, no?
nope - the aggregators/searchers/... run get updates via jabber
I agree with the premise that they should be using pub-sub for (most) api clients, but twitter agrees as wel - and have been working towards it (hence large consumers already using it)