> I think now you are the one confusing timers with the fact > JavaScript is single threading for each tab ... > > I wrote a complete Ajax Guide in 2004 and used LoadVars via Flash > before so hopefully I know these things ...
Certainly possible. And I know nothing about Flash. Only pure JS, which is not Flash, by any means. Tabs have nothing to do with it; window objects, yes. As far as I know, with the exception of Opera, browsers implement one JS thread across all windows. (Pretty sure this is true of IE/FF/Safari; don't know about Chrome). The html5 draft puts forward the goal that from the developers point of view, JS is single threaded. They imply that if a window object is unreachable from another (e.g., because of same origin constraints), it could be running in another thread (since there's no chance of synchronization issues). But all windows that can reach each other must share the same event loop and thus, presumably, the same thread. As far as I can tell, there's some ambiguity about when JS-visible XHR changes can occur. It's clear onreadystate callbacks have to occur on the main thread. What I'm not sure about is whether the XHR readystate attribute can change in the middle of a callback. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
