Not that I am aware of. When writing an app to run properly on a web farm, you should think in the mindset that any given request could hit any of the servers.
You can use a weaker form of load balancing that will lock a user session into a specific server - this is called affinity - such that once they enter the web farm, the server that first services them is the server they use for the rest of their stay. The only problem with that is that when you have to down a server for maintenance, there will be some people that lose their session, or cannot get back into the website. If you don't have any affinity set for your web farm, then you can down a server and all the people that were using it will just be moved to the remaining server(s). They wont even notice a problem. Now, you can share session state amongst servers in a farm using the session service on a central machine, or using the SQL Server session option. So no matter what server your user goes to, their session follows them. If you need any more help with Web farms, let me know, I have been learning for the last couple months after setting ours up. Its just a simple 2 server farm, but the logic scales out. --b Bryan Batchelder eBusiness Consultant ConnectWise, Inc. 813-935-7100 x 425 > -----Original Message----- > From: George Mladenov [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, May 28, 2002 3:00 PM > To: [EMAIL PROTECTED] > Subject: [DOTNET] ASP.NET and HTTP request routing in a web farm > > > Hello, > I am trying to design my web application so that it can be > run in a web farm but I've never actually had any experience > with web farms. I am assuming that in a web farm some load > balancing software (MS Application > Center?) routes HTTP requests to the different web servers > depending on their load. My question is this: once an HTTP > request has been routed to a server and received by my > application, is there a way to re-route this request to > another server in the farm? I know that the > HttpServerUtility.Transfer method in ASP.Net can be used to > terminate the execution of the current page and begin the > execution of another page. As far as I know, however, the new > page must be on the same server. What I would like to do is > to terminate the execution of the current page and begin the > execution of another page but on a specific server from the > farm. Does anybody know if this is possible with the ASP.Net > API? If not, is there some other way of achieving the same > behavior? Regards George > > You can read messages from the DOTNET archive, unsubscribe > from DOTNET, or subscribe to other DevelopMentor lists at > http://discuss.develop.com. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
