> > In the long term we plan to add internal error codes to every non 2** > > response so that the consumer can unambiguously know what error they got > > without munging error message strings (who's language might be changed > > innocently not knowing the consequences). > > That'd be great. Currently I am using regular expression > /Could\s+not\s+follow\s+user/i > If there was any header like X-API-STATUS or X-TWITTER-ERRNO it'd be > so easier to handle error.
I'd actually rather see the response code as part of the response body itself, along with the human-readable portion. -- ------------------------------------ personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Emulate your heroes, but not if they're dead. ------------------------------
