If we need asynchronous calls for a synchronous management, we should use
success as "next call if any" event.
var queue = [function(){/*1*/}, function(){function(){/*2*/}},
function(){/*3*/}, function(){/*4*/}], ajax;
$.ajax(ajax = {
url: './index.html',
success: function() {
queue.shift()();
if(queue.length)
$.ajax(ajax);
}
})
Regards
On Fri, Oct 23, 2009 at 11:50 AM, DBJDBJ <[email protected]> wrote:
>
> Uhm, uhm ... AG is right ... Logically asynchronous events start
> immediately upon firing, but they *finish* at an future undetermined
> point on the time vector. (or "never")
> This is why this paradigm is also called "fire and forget" ... vs
> "wait for return" Synchronous paradigm.
> Therefore: ordered firing of asynchronous events does not guarantee
> ordered finishing.
> This is why they are called "asynchronous" , a.k.a. "out-of-sync" ...
>
> --DBJ
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jQuery Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
