B
Bob Milutinovic
Greetings, folks.
Wondering if someone might be able to shed some light on this without my
having to load up 'n test it for myself.
I have a page calling another with Server.Execute, but depending on what the
outcome of some data checks on that called page is, it may need to "break
out" of the call with a Response.Redirect.
What I want to know is, will this eventually lead to memory leaks because
there's no return to the original calling page?
The environment's a "plain vanilla" IIS installation under Windows Server
2003 Web Edition.
Ultimately I suppose it's not entirely crucial that I need to use this
method; I could always break the original page into two and use
Server.Transfer to avoid the possibility of "left-overs," but I hope someone
here can state with at least a little authority whether or not this problem
might occur.
Thanks in advance,
--
Bob Milutinovic
Cognicom - "Australia's Web Presence Specialists"
http://www.cognicom.tk/
telephone (0417) 45-77-66
facsimile (02) 4727-1898
Wondering if someone might be able to shed some light on this without my
having to load up 'n test it for myself.
I have a page calling another with Server.Execute, but depending on what the
outcome of some data checks on that called page is, it may need to "break
out" of the call with a Response.Redirect.
What I want to know is, will this eventually lead to memory leaks because
there's no return to the original calling page?
The environment's a "plain vanilla" IIS installation under Windows Server
2003 Web Edition.
Ultimately I suppose it's not entirely crucial that I need to use this
method; I could always break the original page into two and use
Server.Transfer to avoid the possibility of "left-overs," but I hope someone
here can state with at least a little authority whether or not this problem
might occur.
Thanks in advance,
--
Bob Milutinovic
Cognicom - "Australia's Web Presence Specialists"
http://www.cognicom.tk/
telephone (0417) 45-77-66
facsimile (02) 4727-1898