Comments on: Ajax and javascript don’t use threads http://www.javascriptkata.com/2007/06/04/ajax-and-javascript-dont-use-threads/ Advanced katas for javascripters Fri, 30 Jul 2010 18:10:52 +0000 hourly 1 http://wordpress.org/?v=3.0 By: jQuery – 當Javascript Ajax遇上Loop | 亞特蘭提斯 Net Atlantis http://www.javascriptkata.com/2007/06/04/ajax-and-javascript-dont-use-threads/comment-page-1/#comment-845 jQuery – 當Javascript Ajax遇上Loop | 亞特蘭提斯 Net Atlantis Fri, 06 Nov 2009 16:57:27 +0000 http://javascriptkata.timmyontime.com/?p=45#comment-845 [...] 解決方法雖然是找到了，但是為什麼會這樣? 可以睇睇國外高手的Blog文: Ajax and javascript don’t use threads Ajax, javascript and threads : the final [...] [...] 解決方法雖然是找到了，但是為什麼會這樣? 可以睇睇國外高手的Blog文: Ajax and javascript don’t use threads Ajax, javascript and threads : the final [...]

]]> By: Ajax y Javascript no usan hilos http://www.javascriptkata.com/2007/06/04/ajax-and-javascript-dont-use-threads/comment-page-1/#comment-302 Ajax y Javascript no usan hilos Thu, 20 Sep 2007 15:41:19 +0000 http://javascriptkata.timmyontime.com/?p=45#comment-302 [...] no es así. Lo cierto, tal y como hemos podido leer en algún que otro artículo es como si la “máquina” o hilo de ejecución que interpreta el javascript se [...] [...] no es así. Lo cierto, tal y como hemos podido leer en algún que otro artículo es como si la “máquina” o hilo de ejecución que interpreta el javascript se [...]

]]> By:   A long-time javascript function fires an XHR call by The Third Part http://www.javascriptkata.com/2007/06/04/ajax-and-javascript-dont-use-threads/comment-page-1/#comment-301   A long-time javascript function fires an XHR call by The Third Part Mon, 18 Jun 2007 03:34:45 +0000 http://javascriptkata.timmyontime.com/?p=45#comment-301 [...] 从Dan Simard的两 篇文章以及读者的一些评论中，我们看到在一个执行时间很长的javascript函数（比如longtimeF()）中的某个时间点执行一个ajax的请求。可以肯定的是browser肯定会启动一个threads来执行这个XHR的异步请求，这个threads随着response的到来而结束，而callback函数并不在这个线程内执行。 [...] [...] 从Dan Simard的两 篇文章以及读者的一些评论中，我们看到在一个执行时间很长的javascript函数（比如longtimeF()）中的某个时间点执行一个ajax的请求。可以肯定的是browser肯定会启动一个threads来执行这个XHR的异步请求，这个threads随着response的到来而结束，而callback函数并不在这个线程内执行。 [...]

]]> By: Ajax and javascript don’t use threads | Javascript Kata at thirstymind.org http://www.javascriptkata.com/2007/06/04/ajax-and-javascript-dont-use-threads/comment-page-1/#comment-300 Ajax and javascript don’t use threads | Javascript Kata at thirstymind.org Fri, 15 Jun 2007 23:53:51 +0000 http://javascriptkata.timmyontime.com/?p=45#comment-300 [...] Ajax and javascript don’t use threads | Javascript Kata: according to this i’m not cool, i want to be cool, but again a decision i didn’t have input on and don’t have enough time to put up a fight. [...] [...] Ajax and javascript don’t use threads | Javascript Kata: according to this i’m not cool, i want to be cool, but again a decision i didn’t have input on and don’t have enough time to put up a fight. [...]

]]> By: Norman http://www.javascriptkata.com/2007/06/04/ajax-and-javascript-dont-use-threads/comment-page-1/#comment-299 Norman Fri, 15 Jun 2007 02:27:56 +0000 http://javascriptkata.timmyontime.com/?p=45#comment-299 Those are thread communication stuffs. Request thread send a message to main thread and ask main thread to fire the onComplete event. Those are thread communication stuffs.

Request thread send a message to main thread and ask main thread to fire the onComplete event.

]]> By: Ajax Girl » Blog Archive » Ajax, javascript and threads : the final truth http://www.javascriptkata.com/2007/06/04/ajax-and-javascript-dont-use-threads/comment-page-1/#comment-298 Ajax Girl » Blog Archive » Ajax, javascript and threads : the final truth Thu, 14 Jun 2007 12:47:14 +0000 http://javascriptkata.timmyontime.com/?p=45#comment-298 [...] Simard has been writing about threading and JavaScript and came up with his Final [...] [...] Simard has been writing about threading and JavaScript and came up with his Final [...]

]]> By: Pablo Cabrera http://www.javascriptkata.com/2007/06/04/ajax-and-javascript-dont-use-threads/comment-page-1/#comment-297 Pablo Cabrera Thu, 14 Jun 2007 11:34:06 +0000 http://javascriptkata.timmyontime.com/?p=45#comment-297 To prevent the alert, confirm, etc... from pausing the script execution, you could overwrite the default function with some custom dialogs, so you never get the default dialogs halting your script. This way you can guarantee that your callbacks will execute just after your current running code To prevent the alert, confirm, etc… from pausing the script execution, you could overwrite the default function with some custom dialogs, so you never get the default dialogs halting your script. This way you can guarantee that your callbacks will execute just after your current running code

]]> By: Rob Desbois http://www.javascriptkata.com/2007/06/04/ajax-and-javascript-dont-use-threads/comment-page-1/#comment-296 Rob Desbois Tue, 05 Jun 2007 08:25:00 +0000 http://javascriptkata.timmyontime.com/?p=45#comment-296 This is an important point - not guarantee-able of course, given that it's totally down to browser implementation, but I'd hate to meet the browser that spawned a new thread for each AJAX request! It should also be remembered that whilst you need to bear in mind the volatility of shared variables, the ordering of AJAX responses should *never* be relied on or even thought about - that's what asynchronous means! This is an important point – not guarantee-able of course, given that it’s totally down to browser implementation, but I’d hate to meet the browser that spawned a new thread for each AJAX request!

It should also be remembered that whilst you need to bear in mind the volatility of shared variables, the ordering of AJAX responses should *never* be relied on or even thought about – that’s what asynchronous means!

]]> By: BK http://www.javascriptkata.com/2007/06/04/ajax-and-javascript-dont-use-threads/comment-page-1/#comment-295 BK Mon, 04 Jun 2007 16:30:18 +0000 http://javascriptkata.timmyontime.com/?p=45#comment-295 I agree with you on the fact that the main thread will be used BUT, from my experience, I'm not quite sure on the order of the requests... Maybe it depends on the browser used but using IE, I often got functions interupted by the new incoming response. Briefly, say I have CallPage1, CallPage2 and DoSomething. Both CallPage are async. CallPage1 called CallPage2 called DoSomething called CallPage1 Returned (DoSomething is now paused) DoSomething ended CallPage2 Returned This is important to know if you use any shared variable because you can't rely on the fact that it won't change during the process of your sub. If it's not clear, tell me. I agree with you on the fact that the main thread will be used BUT, from my experience, I’m not quite sure on the order of the requests… Maybe it depends on the browser used but using IE, I often got functions interupted by the new incoming response.

Briefly, say I have CallPage1, CallPage2 and DoSomething. Both CallPage are async.

CallPage1 called
CallPage2 called
DoSomething called
CallPage1 Returned (DoSomething is now paused)
DoSomething ended
CallPage2 Returned

This is important to know if you use any shared variable because you can’t rely on the fact that it won’t change during the process of your sub. If it’s not clear, tell me.

]]>