Thanks.

On May 31, 6:55 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
> To add to Arnaud's comment...
>
> There was a past where Twitter's error messages were very unstructured.
> Newer API features follow a more descriptive, human-readable,
> and programmatically consumable error structure. Version 1 of the API has
> mixed error response formats depending on when the feature was introduced
> (some introduced before versioning was present in the API). One can expect
> that future versions of the API will have a unified error response structure
> that will be able to adapt as needs and wisdom change.
>
> I know that it's hard to pre-prepare your code for error conditions you may
> not typically come across and we'll work this week on better documenting
> both the less structured and more structured error responses for everyone's
> benefit.
>
> @episod <http://twitter.com/episod> - Taylor Singletary
>
> On Tue, May 31, 2011 at 9:47 AM, Arnaud Meunier <arn...@twitter.com> wrote:
> > Hey Maomor,
>
> > The Error codes don't follow a "logic" in particular.
> > I'd recommend that you rely on the (error message string + HTTP Code)
> > combination.
>
> > Hope that helps,
> > Arnaud / @rno <http://twitter.com/rno>
>
> > On Mon, May 30, 2011 at 6:05 AM, Maomor <maldw...@gmail.com> wrote:
>
> >> I do not understand why twitter will not tell us how we should handle
> >> their error codes.
>
> >> Our applications need to distinguish between an error response such as
> >> 7 ( No data for a place ) and 10 ( Geo services currently
> >> unavailable ).
>
> >> Can Twitter understand that we have the need to do this ?
>
> >> And, if so, why do they remain silent on this issue ?
>
> >> --
> >> Twitter developer documentation and resources:
> >>https://dev.twitter.com/doc
> >> API updates via Twitter:https://twitter.com/twitterapi
> >> Issues/Enhancements Tracker:
> >>https://code.google.com/p/twitter-api/issues/list
> >> Change your membership to this group:
> >>https://groups.google.com/forum/#!forum/twitter-development-talk
>
> >  --
> > Twitter developer documentation and resources:https://dev.twitter.com/doc
> > API updates via Twitter:https://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >https://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >https://groups.google.com/forum/#!forum/twitter-development-talk

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Reply via email to