bump Would be good to hear from Twitter API devs on this.
On Apr 27, 12:50 am, André Luís <andreluis...@gmail.com> wrote: > As long as they keep this from affecting other non-API endpoints, > > +1 > > Other than that, it could be disastrous. > > -- > André Luís > > > > On Tue, Apr 27, 2010 at 12:04 AM, rmanalan <rich.manal...@gmail.com> wrote: > > +1 > > > On Apr 26, 5:01 am, Remy Sharp <r...@leftlogic.com> wrote: > >> Is there any thoughts towards setting the following header on the > >> Twitter API server: > > >> Access-Control-Allow-Origin: * > > >> For those of us developers working with web technology in closed > >> environments (such as PhoneGap) we can useXHRcontrolled requests to > >> Twitter - i.e. we can read headers (like the X-RateLimit-Remaining), > >> abort requests, handler timeouts and handle the all important fail > >> whale coming back instead of a JSON response saying it's failed. > > >> Such a small change would open up using the web to access the API. > > >> What do you think? > > >> - Remy. > > >> -- > >> Subscription > >> settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
