The amount of time it takes for them finish is dependent upon how long it takes the server to process the request plus any other network-related latencies. If you start your requests and they (more or less) start at the time time, that's all you can bet on. When they complete (and in what order) is completely dependent on processing time. Just because you start "request A" first doesn't mean that "request B" won't finish first...
Hope this helps, ~Philip On Mon, Aug 8, 2011 at 2:00 PM, Sid-ahmed D <[email protected]>wrote: > Could you please show me a example ? > Because, i try and i try and ... nop .. > > I start 2 requests "simultaneously" to 5 secondes. > I see in console log, 2 requests start "simultaneously" but the first > finish to 5sec and seconds to 10 sec ... > They start "simultaneously" but execute in 'chain' ... > > On Aug 8, 8:49 pm, Sean McArthur <[email protected]> wrote: > > Don't bother with the chain option, in this case. You can run two > > asynchronous requests simultaneously. They might not finish at the same > > time, as that depends on the server. > -- http://lonestarlightandsound.com/
