Brad Wilson [mailto:[EMAIL PROTECTED]] wrote:
> > Response.Redirect will require a roundtrip to the browser, correct? > > How do you do the same thing without the roundtrip? > > If it's not on the same machine, then there's nothing > built-in that can do it for you. Of course, you could open up > an HTTP request to the second host on your own and funnel the > results back as though you'd actually processed the request > yourself. To the best of my knowledge, though, there isn't > anything built-in that will do this. Brad's answer is correct, but I'm not 100% that you're asking him the right question anymore. There is HttpServerUtility::Transfer, which is usually accessed via HttpContext::Server.Tranfer. This allows the request to be redirected within the SAME machine. So if you make the decision in the executing handler (Page) that you would like processing to be handed off to another handler (Page) on the SAME machine, that's how you'd do it. Perhaps you could supply us with some more details about exactly what it is you're trying to accomplish and we can offer a better solution. HTH, Drew .NET MVP You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
