Timeline for OBSOLETE - Build an app with Soapi.JS and gain praise and adulation. And some rep
Current License: CC BY-SA 2.5
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 13, 2017 at 12:25 | history | edited | CommunityBot |
replaced http://stackapps.com/ with https://stackapps.com/
|
|
Jun 16, 2010 at 5:32 | comment | added | Mark Henderson | Can someone -1 this just so that it sits at the bottom of the list and doesn't get the bounty | |
Jun 14, 2010 at 22:20 | comment | added | Mark Henderson | @code, as usual everything you've said sounds right... I was just too late into the design of my application to change it to one of the methods you mentioned. I didn't really put much thought into the idea to be honest, but I can see the problem that this is faced. I guess the answer is "no - next time design your app to use the library properly" ;) | |
Jun 14, 2010 at 16:24 | comment | added | Nathan Osman | Writing a blocking jsonp call seems like it shouldn't even be possible :) | |
Jun 14, 2010 at 10:12 | comment | added | Sky Sanders | And I typically chain calls that would otherwise be suited to be run synchronously. e.g. make the next call from within the success function. With a little imagination and a flag or two this can serve such a purpose. And as far as a queue goes, I have an implementation somewhere in my qunit code. I will try to dig it up. | |
Jun 14, 2010 at 8:13 | comment | added | Sky Sanders | Aside from the obvious dark pit of hades into which I would be thrown if I were able to implement a blocking call in JS, how to implement a blocking call in a jsonp wrapper is not immediately apparent to me. The api calls are made via jsonp, injected script tags, not XMLHttpRequest. Do you have any ideas? I have implemented a viable blocking call in the silverlight version, but then I have threads and am able to force the call to be made on a thread other than the UI thread. No such animal in regards to browsers (workers in chrome) in general distribution any time in the near future. | |
Jun 14, 2010 at 7:18 | comment | added | Nathan Osman | Hey, the rest of us haven't given up on the monitor either :) | |
Jun 14, 2010 at 6:57 | history | answered | Mark Henderson | CC BY-SA 2.5 |