At www.footballfanatics.com we used one "gateway" machine, which actually ran WiTango. It would look at a table of available machines and redirect the user to "www1." or "www2." etc.
This is called "Sticky-IP" technique. The disadvantage is that you can't change servers mid-session. So if you're at the site and the box goes down to have to come back to the site manually and get redirected to an active machine.
The advantage of using WiTango to do it than round robin DNS is that we made outselves a nice little web interface to manage the server pool and we didn't have to depend on any third-party DNS solutions.
There is a way to set WiTango up with "high availability" mode, meaning any one machine failure is transparent and session variables are transportable between servers, but I have no idea how to do it.
- James.
Rich <[EMAIL PROTECTED]> wrote:
Does anyone have experience with using round robin dns with WITANGO? Any issues with retaining user variables?
rich
->|- Diodeus, noun: the Greek God of diodes, as opposed to Typos, the Greek God of typing mistakes. He keeps moving the keys on me.
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
