An additionnal round trip :
- Response.Redirect "tells" the browser it should go to another page
- the browser then go to this page
A replacement is Server.Transfer if you called "processing only" pages using
Response.Redirect. I would keep Response.Redirect to display th final UI
related page (the drawback of Server.Transfer is that the browser doesn't
know the real url of the page).
Patrice
Bonj said:
If I use Response.Redirect, does this cause an additional round trip to
A replacement is Server.Transfer if you called "processing only" pages
using
Yes, but you have to watch if you are passing values in querystring. If you
use Server.Transfer url in browser doesn't change, so querystring is always
the same. I had once problem with it.
I read something on 4guysfromrolla that Server.Transfer is "native to windows 2000" or something and that it isn't as good, I've gone with Response.Redirect and it seems to be OK
Was new in IIS 5.0. It's just sometimes used IMO incorrectly instead of
Response.Redirect to save a round trip but could have its proper usage prior
the .NET area (processing only pages). With ASP.NET, Server.Transfer should
IMO never be used...
Patrice
Bonj said:
I read something on 4guysfromrolla that Server.Transfer is "native to
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
