Hi Nick Thanks so much that sorted it all out.....it's been bugging me for the last two days, but had to put it aside to continue with other work. Just ran a test now and it works as expected.
I get the jist of what was going on now but I'll need to research it a little more indepth to fully understand what was happening on the server side. Thanks again much appreciated. Sak On Aug 11, 12:23 pm, Nick Fitzsimons <n...@nickfitz.co.uk> wrote: > 2009/8/11 sak <saks...@gmail.com>: > > > > > Thats the thing, I don't want the results coming back in order. I am > > trying emulate them coming back unordered, but they are coming back > > ordered. I was digging deeper yesterday and discovered the results are > > linked to an aspsessionid cookie that is created from the asp pages > > (don't fully understand it yet) but through elimination I determined > > if I delete this cookie everytime it is generated, then the AJAX calls > > behave normally - the calls work asyncronously. If the cookie exists > > then the AJAX calls act syncronously which is not what I want. If > > anybody has any experience in this..... > > I assume you're using Classic ASP rather than ASP.NET? If so, the > reason your first (10s) call delays the response to the second (1s) is > that ASP's session tracking is enabled by default, and its session > object does not support concurrent access by multiple threads. Thus, > when the server starts a thread to handle the second (1s) request, > that thread is blocked waiting for the session object associated with > your client (via the session cookie) to be released by the first (10s) > request's thread. So this is just an effect of a limitation in the > server-side technology, and nothing to do with the browser or jQuery. > > You can disable session tracking for your tests using the > @ENABLESESSIONSTATE directive: > <http://msdn.microsoft.com/en-us/library/ms525847.aspx>. > > Regards, > > Nick. > -- > Nick Fitzsimonshttp://www.nickfitz.co.uk/
