H
harry
Hello,
just been trying to find the answer to what I think should be a rather
simple question but can't seem to find a definite yes or no.
Anyway question is, are asp dot net pages (aspx) subject to the same script
timeout that normal asp pages are?
IE after the default 90 seconds would the aspx through a timeout or will
they carry on until an error or the page has
finished running.
I tried the following lowering the script timeout to 30 seconds and then
adding the following line
Thread.Sleep(120000) (which should tell the thread to sleep for 2 minutes)
but it carried on till the sleep command finished and displayed the page as
normal.
If it is the case that the timeout does not apply to aspx pages, is there
some property in the web.config that can set a time
or is best practices to have something within the classes that knows when
and how to stop a particular process if it appears to be
taking to long.
are there any msdn articles that discuss these things (I haven't had much
luck so far but it is monday morning). Or is asp.net sufficiently
different to not require the web server to timout if an action takes too
long(in asp it was there to safeguard future requests from having
to wait to long).
Harry
just been trying to find the answer to what I think should be a rather
simple question but can't seem to find a definite yes or no.
Anyway question is, are asp dot net pages (aspx) subject to the same script
timeout that normal asp pages are?
IE after the default 90 seconds would the aspx through a timeout or will
they carry on until an error or the page has
finished running.
I tried the following lowering the script timeout to 30 seconds and then
adding the following line
Thread.Sleep(120000) (which should tell the thread to sleep for 2 minutes)
but it carried on till the sleep command finished and displayed the page as
normal.
If it is the case that the timeout does not apply to aspx pages, is there
some property in the web.config that can set a time
or is best practices to have something within the classes that knows when
and how to stop a particular process if it appears to be
taking to long.
are there any msdn articles that discuss these things (I haven't had much
luck so far but it is monday morning). Or is asp.net sufficiently
different to not require the web server to timout if an action takes too
long(in asp it was there to safeguard future requests from having
to wait to long).
Harry