George Mladenov 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. > The problem that I am trying to solve is data-dependent routing. I would > like to share state between HTTP requests but I _do not_ want to use the > state sharing facilities provided by ASP.Net. I'm not sure what you mean. Among the session station options given to you by ASP.net, there's one that'll stash state in a database for just this type of work (web farms). Of course, there's no reason you need to use ASP.net's version of session state at all. You could concoct anything you wish, but I'm hard-pressed to think of a scenario that can't be addressed by what's already there (since you have access to both client-side state -- cookies, server-side state -- session, and database-managed state). Brad -- Read my web log at http://www.quality.nu/dotnetguy/ You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
