Josh, This will not protect us against a case where something central to Twitter functioning malfunctions, but it will protect us against new or changed features malfunctioning.
Dewald On Dec 17, 10:45 pm, Josh Roesslein <jroessl...@gmail.com> wrote: > I am not sure how beneficial this would really be. Versioning from > what I understand is for changes to the > API that might break applications that have not yet updated. It > wouldn't really provide any security against bugs/quirks > in Twitter's backend which can cause downtime. So even older versions > might be affected just as much as newer versions because > down under they both use the same code, its just exposed differently > from version to version. > > I have no idea how things work under the covers so maybe this could > work. I'd take any security against down time I can get. :) > > Josh > > On Thu, Dec 17, 2009 at 8:35 PM, Dewald Pretorius <dpr...@gmail.com> wrote: > > The yo-yo ride of the retweet API gave me this idea. It depends on > > proper versioning of the API by Twitter. > > > Twitter creates an API call that returns the current working API > > version. We query that method and use that version of the API for our > > calls. > > > If something goes down, Twitter simply pushes out the version number > > of an older API version, which is still working correctly. Our systems > > will then automatically fall back to using that older version, until > > Twitter again pushes out the new version number when it's back online. > > > Dewald
