Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Why dont you daisychain your events? That way all the callback events are injected withouy delay. Now you have the risc that the ajax fetching is complete before a complete handler is assigned and the processes mismatch. Commented Jul 5, 2012 at 22:02
  • I know... but after having seen the internet grow since IE4 and netscape nothing suprises me anymore... I've seen the most impossible things work(for example ie and the zoom:1 thing). If it doesn't work one way, another way it might, and somethimes you have to do the impossible thing to achieve somthing... Browser differences, Who doesn't love them. Commented Jul 6, 2012 at 8:33
  • Plus, it might be "unlikely" but remember that javascript is a single thread process without web workers, and all other execution gets delayed when something else jumps up front(an image slider, a loading bar appearing, etc...) and that way your getxhr.xxxx functions might get delayed because triggers fire and other events get more priority... With a daisychain you make sure everything in the chain is handled and set before the document thinks it can execute the next item on the stack. Commented Jul 6, 2012 at 8:38
  • See edit. The POSTS are daisy chained so they don't over-lap. The reads can't overlap and messages will wait for up to 60 seconds while we handle the front of the queue, so daisyhchaining is not necessary. Commented Jul 6, 2012 at 15:19