I'm with you Simon... I was wondering where this thread was going... I decided to do a little test for myself, and fortunately, (or unfortunately depending on how you want it to behave) Robert Sfeir's first response was incorrect.
A second taf request will not interrupt the first taf request. At least not
in my environment.
Client: WinXP IE6
Server: NT4 IIS T2K
Here's the scenario, 3 taf files..
test_from.taf
-------------
1. link to test_long.taf
2. link to test_short.taf
3. Assign user$testvar = NOT DONE
test_long.taf
-------------
1. big useless loop from 1 - 10000
- output the word "loop" - NO PUSH
2. user$testvar = DONE
test_short.taf
--------------
1. output user$testvar
That's it, you put these three files on your server, and hit test_from.taf.
You see two links, click on the "long" link. The loop in test_long.taf
takes about 12 seconds to execute (on my server right now), so being the
impatient luser that i am, i decide to click on the "short" link.
Which promptly returns "NOT DONE"
So i refresh the page... "NOT DONE"
again "NOT DONE"
again "DONE"!
So, the original request that I as the user, abandoned by clicking on
another link still continues to run until the taf is done executing...
This is how I expected this to operate, but never got around to making a
test case.
This is why a something that takes a long time to execute on your site can
cause more load then you think, because some of your users will be
impatient, and hit reload, causing the server to take even longer, because
now it executing two of those requests.
I've attached my small test case for anybody who want's to try it out for
themselves...
----- Original Message -----
From: "Simon Boddy" <[EMAIL PROTECTED]>
To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]>
Sent: Wednesday, September 25, 2002 4:01 AM
Subject: RE: Witango-Talk: a random question
> Hi list,
> To sumarise, the original question here was...
> What happens when a user initiates a second request from a page before the
> first request has been executed and page returned. Bill Conlon's reply
> proposed a mechanism for blocking the execution of the second request.
This
> sounds fine and dandy, however Robert Sfeir's first response to this
> question suggested that the execution of the first request would be
> interrupted when the second request was received.
>
> Does this happen? What is the mechanism? How would Tango associate the two
> requests? There is nothing in the requests that identifies them as
> originating from the same window. Is there a mechanism for a user agent to
> cancel a request in progress? Wouldn't Tango execute and return results
and
> return the page, then it would be up to the browser to ignore the response
> in favour of the second request?
>
> I've suddenly started fretting. I hope it's just coz I'm not properly
awake
> yet.
>
> Regards, Simon
>
>
> ********************************************************************
> This message is intended only for the use of the person(s) ("the intended
> recipient(s)") to whom it is addressed. It may contain information which
is
> privileged and confidential within the meaning of applicable law. If you
> are not the intended recipient, please contact the sender as soon as
> possible. The views expressed in this communication may not necessarily
> be the views held by LGCSB (Local Government Computer Services Board).
>
> Any attachments have been checked by a virus scanner and appear to be
> clean.
> Please ensure that you also scan all messages, as LGCSB does not accept
> any liability for contamination or damage to your systems.
> ********************************************************************
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
test.zip
Description: Zip compressed data
