On Fri, 3 Sep 2010 09:12:32 -0700 (PDT) Dewald Pretorius <dpr...@gmail.com> wrote:
> Twitter folks, how are you going to ensure that t.co links are not > affected by over-capacity situations on your infrastructure? > > If you're routing t.co links through your existing infrastructure, > absolutely *everyone's* links are going to be broken when you start > throwing fail whales, even when the link is clicked in third-party > applications. > > Are you running t.co on its own separate and dedicated infrastructure? > Ah, that brings up the next idea of how to enhance my application :) It wouldn't be all that hard to keep a cache/database of all the t.co links seen in a user's incoming timeline, and their resolution. The user would then have a private link resolution database, to protect against such service outages. Seems pretty straightforward, perhaps people should do that sort of thing. Bernd -- Bernd Stramm bernd.str...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
