The main thing that's changing with the new release of the API is the URL scheme. We're cleaning things up, moving things around, making the whole thing more RESTful. I'll confer with @mzsanford and see about sharing our proposed set of URLs/methods.
Generally, though, we're still the same service and we've still got the same data to share with API clients, so the actual response formats themselves should change very little, save some new attributes popping up. Our main goal is moving the API onto a high-performance app server and optimizing such that we no longer have to burden all but the most aggressive clients with rate limiting. On Wed, Dec 3, 2008 at 21:16, dean.j.robinson <[EMAIL PROTECTED]> wrote: > > The rewrite of the api has been on the cards for a while, and I've > kind of avoided doing any major work on Hahlo until I knew what was > happening, however it got the better of me last weekend and I began > work on Hahlo 4 which itself is a complete re-write. > > Given that its a re-write how much do you see it changing as far as > how developers access it, ie. will the json,xml etc feeds still be the > same, will there be new/different parameters, or is the whole thing > just going to be completely new/shiny/fantastic? > > And even though I do very much like the authentication system I wrote > on the weekend, I might start to investigate OAuth in preparation for > its appearance. > > > > On Dec 3, 9:31 am, "Alex Payne" <[EMAIL PROTECTED]> wrote: >> Sure, I'll talk to the UX folks about writing some of that up. OAuth >> is still in its early stages, and it seems most every organization >> that implements it ends up taking some slightly different paths. >> >> On Tue, Dec 2, 2008 at 13:03, Christopher St John <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> > On Tue, Dec 2, 2008 at 2:27 PM, Alex Payne <[EMAIL PROTECTED]> wrote: >> >> >> Additionally, Matt has been working with our User Experience (UX) team >> >> on a beta of OAuth support. The UX component of this work is almost >> >> complete, and we should be ready for our first deploy in the next week >> >> or ten days. >> >> > Nifty. >> >> > Anything y'all can share about the thinking behind your OAuth UX >> > decisions would be very helpful (not just how it ends up looking, but >> > the sorts of things that were of concern, differerent options you >> > considered, etc). That stuff's pure gold for others facing similar >> > sorts of decisions. Not totally on topic, I'm just saying... >> >> > -cks >> >> > -- >> > Christopher St. John >> >http://artofsystems.blogspot.com >> >> -- >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
