What is the difference between Server.Transfer and Response.Redirect? Why would I choose one over the other?

 Posted by Poster on 7/1/2008 | Category: ASP.NET Interview questions | Views: 6849

In earlier versions of IIS, if we wanted to send a user to a new Web page, the only option we had was Response.Redirect. While this method does accomplish our goal, it has several important drawbacks. The biggest problem is that this method causes each page to be treated as a separate transaction. Besides making it difficult to maintain your transactional integrity, Response.Redirect introduces some additional headaches. First, it prevents good encapsulation of code. Second, you lose access to all of the properties in the Request object. Sure, there are workarounds, but they're difficult. Finally, Response.Redirect necessitates a round trip to the client, which, on high-volume sites, causes scalability problems.
As you might suspect, Server.Transfer fixes all of these problems. It does this by performing the transfer on the server without requiring a roundtrip to the client.

Source: http://groups.msn.com/MumbaiUserGroup/aspnetfaqs2.msnw | Asked In: Many Interviews | Alert Moderator 

Comments or Responses

Login to post response