Load balancing is done at the point of first request (one without a user reference or cookie), and then selected randomly from the list of services available. You should note that going from a non-load-balanced to a load-balanced environment has its issues, so be ready to deal with them. (if you depend on shared scope variables to be available to all your users, for example, you will have to write tools that update both services at the same time). Once a USR and/or cookie has been establish, the same server is always used for that user's session. The server information is part of the USR string (increasing it from 24 characters to 36). Robert
_____ From: Fogelson, Steve [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 09, 2007 2:30 PM To: [email protected] Subject: Witango-Talk: Load Balancing/Migration I have 2 Witango servers. One is running Version 5.0.65 R:Base Edition and one is Version 5.5 Standard Edition. As I have time I am moving apps from 5.0.65 to 5.5, but am starting to overload the 5.5 server at times. Budget does not allow me to purchase an additional server at this time. If I purchased another 5.5 Standard license, could I load it on the 5.0.65 server and set up load balancing for 5.5 between the 2 servers and still run apps under 5.0.65 on the one server? This would allow me to migrate the remaining apps to 5.5 without putting an undo load on the existing 5.5 server. How does Witango determine which server to assign a client to in a Load Balancing environment? Is it based on server availability (response)? I am wondering if for a burst of time that the 5.0.65 apps are using a lot of resources. Can I also run the 5.5 apps using both R:Base and MySQL databases in the load balancing environment? Thanks Steve Fogelson Internet Commerce Solutions ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
