Interestingly, when I click the link in Google Chrome, it just hangs loading...curl works fine though.
So try curl, see what happens :-) David On Oct 1, 12:37 pm, Vision Jinx <vjn...@gmail.com> wrote: > Hi David, > > Yes, that's what I am asking but my experience is different. o.O > > When I click the links I provided the one I get the json data > (download file w/json) while the other I just get a 404 page saying > > File not found > Firefox can't find the file > athttp://twitter.com/statuses/user_timeline.json?id=twitter2222&callbac... > > (I have tried it on different computers, OSs -Linux and Windows- and > networks too. I didn't try via curl though, will when I get back > home.) > > When I request the same thing in my app (http://www.visionjinx.net/? > pid=miniapps) I just get nothing and my app stays on "loading..." > which tells me my callback is never called as it should clear that > loading... message. (try the twitter2222 by user name on my app to > see) > > Any thoughts? > > Cheers! > Vision Jinx > > On Sep 30, 7:12 am, David Somers <jal...@gmail.com> wrote: > > > > > I might be understanding wrong, but when I do: > > > $ curl "http://twitter.com/statuses/user_timeline.json? > > id=twitter2222&callback=bar" > > > I get: > > > bar({"request":"/statuses/user_timeline.json? > > id=twitter2222&callback=bar","error":"Not found"}) > > > Isn't that what you're asking for? > > > David > > > On Sep 30, 10:53 am, Vision Jinx <vjn...@gmail.com> wrote: > > > > Hi group and Twitter team, > > > > Still having issues working with the Twitter API, main concerns are > > > things like when making JSONP requests to say accounts that don't > > > exists (like in the case of a typo etc) I just get a null header or > > > 404 page. > > > > To me when making a RESTful JSONP query it should still return a JSON > > > string of some sort with the error code and reason or message etc. > > > > Twitter, can you please implement this into your API so it will return > > > JSON on failed calls, getting a null header or a 404 page just breaks > > > my apps since no data is ever returned as JSON. > > > > Eg.http://twitter.com/statuses/user_timeline.json?id=twitter2222&callbac... > > > > I would like to see at minimum... > > > > bar({"error":"404","status":"Sorry, that user doesn’t exist!"}); > > > > (or account deleted or suspended user etc etc etc) > > > > It seems without any data being returned I need to put my queries on > > > timers with a retry flag or something (not what I really want to do) > > > and such to try again to see if there was latency in the API and then > > > generate an unknown error with an "Ummm... Something did not happen > > > but I don't know what" message o.O These extra requests also seem to > > > count towards the API limits too. > > > > Any suggestions from other Devs on how you deal with this please let > > > me know also (since your callback function never gets called) and am > > > hoping this will get resolved by the Twitter team soon. (does not seem > > > like a hard fix to implement) > > > > I at least see with the JSONP search queries they have this.... > > > > Eg.http://search.twitter.com/search.json?q=hsdfkhksjdfusdh&callback=bar > > > > Retruns: > > > > bar({"results":[],"max_id":-1,"since_id":0,"results_per_page": > > > 15,"page":1,"completed_in":0.010536,"query":"hsdfkhksjdfusdh"}); > > > > Thanks for any suggestions! :) > > > > Cheers! > > > Vision Jinx
