What is the difference between Server.Transfer and
Response.Redirect? Why would I choose one over the other?
- 8 Answers
- 10560 Views
- Siebel Systems, I also Faced
- E-Mail Answers
Answer Posted / kumar saurabh
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.
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
can we remote debug applications with the remote debugger installed with vs.net 2002, with vs.net 2003?
In which event of the page viewstate is available?
Explain the Order of events in an asp.net page?
What are the benefits of Razor View?
Explain significance of routing? : asp.net mvc
Describe the disadvantage of cookies.
How do I use a proxy server when invoking a web service?
What are the advantages of using Master Pages?
Explain cashing in asp.net.
What does asp.net stand for?
What are the uses of reflection?
What is the purpose of master page?
When we use cookie less session? Explain its working?
What is difference between rest and soap?
What is web router?
