That's the weird thing about the calls: it doesnt matter what i do on my server side ( ie. a sleep-command) the second call only renders when the firstcall has returned data... ?
And about the ajaxSetup part: the async is by default already true, so all calls should be called async-ed... I'm at a loss! On 10 dec, 05:30, George <[EMAIL PROTECTED]> wrote: > I do not know about php but asp and asp.net serialize access to the > same Session. (basically same browser). > So it would be normal. And problem on server side. > > George. > > On Dec 9, 8:27 am,RobinSpeekenbrink <[EMAIL PROTECTED]> wrote: > > > I have a (stupid) problem: i have the follwing short script: > > $(window).load(function() { > > $("#div1").load('/xmlHttp.php?action=getLoad'); > > $("#div2").load("/xmlHttp.php?action="+ $("input > > [name='selectType']").val()); > > > }); > > > What this does: it calls the central xmlHttp url to fetch data. Simple > > right? Except that the first call can stall the second? The second > > call will finish only when the first is already done? > > > It seems that the second call waits for the first to be done? (ór its > > just a widly strange coincidence that the two calls each take the > > exact amount of time according to firebug) > > > the overall settings are as follows: > > $.ajaxSetup({cache: false}); > > > If i rearrange the first call áfter the second the results are as > > expected: #div2 is filled quickly while div1 is still loading... > > > Is this a bug or something else?