Re: Server.Transfer vs. Response.Redirect
- From: "Patrice" <nobody@xxxxxxxxxxx>
- Date: Wed, 15 Jun 2005 16:46:29 +0200
Response.Redirect tells the client the new URL that should be hit.
Server.Transfer is server side and the client doesn't know the new location
which could be a problem.
Still I've got mayself a hard time to find out a legitimate use for
Server.Transfer / Server.Execute. I always thought it's here mainly for
legacy as it always looks like to me the reason is that you embedded some
processing in a particular ASPX page which is not especially desirable ?
Hopefully someone will pop up with a legitimate use I didn't thought
about...
Patrice
--
"Terry Olsen" <tolsen64@xxxxxxxxxxx> a écrit dans le message de
news:%23oDouTbcFHA.2288@xxxxxxxxxxxxxxxxxxxxxxx
> Since both methods seem to produce the same results, in which cases
> would you prefer one over the other? The only thing I would think is
> using Server.Transfer because of some browsers blocking redirects.
>
> *** Sent via Developersdex http://www.developersdex.com ***
.
- References:
- Server.Transfer vs. Response.Redirect
- From: Terry Olsen
- Server.Transfer vs. Response.Redirect
- Prev by Date: [Newbie Question] Populating Textbox.text from a dataview using column names?
- Next by Date: Re: PostBack "Please Wait..." Message.
- Previous by thread: Server.Transfer vs. Response.Redirect
- Next by thread: Re: Server.Transfer vs. Response.Redirect
- Index(es):
Relevant Pages
|
