Thanks for looking at this Jörn, but then the ajaxQueue plugin becomes rather moot, doesn't it? Also I was trying to make a plugin of the code above. I "just" needed a way to ensure the initial call had come back before continuing. And for a few minutes there I thought the queue plugin was going to do that for me transparently: Queued Ajax requests. * A new Ajax request won't be started until the previous queued request has finished.
I guess I'll just have to wrap my head around how to transport the jquery selected elements into a nested ajax calls and do the $.each loop inside the initial success function (I'm talking about the plugin). Vielen Dank fuer die Hilfe CIAO Angelo On Feb 11, 2:01 pm, Jörn Zaefferer <[EMAIL PROTECTED]> wrote: > sozzi schrieb:> I guess I must be using the plugin wrong. I am trying to make > sure > > that the second AJAX request does not start until the Session.ID > > variable (from the first call) was set. > > The second call never gets properly executed (below) because > > Session.ID is still undefined.... > > So I guess I'm doing something wrong still, but what exactly? > > You should try to start the second request in the callback of the first. > That gurantees the right synchronization. > > Jörn
