Quote:
Originally posted by pancake7
One last question for x3m. Does your script work with multiple load balanced servers? We have our "gallery" page served off of a load balanced cluster, then the video files are served off of other dedicated video servers. So each request to the gallery page will go to a different server, and the request to the video file itself goes to a completely different set of servers. My guess is that your script is storing the client info on the server, so it only works if both hits go to the same server, which of course won't work for any large scale site using load-balancing like Cisco's Local Directory or a Coyote Point Equalizer. The logistics of sharing the client-info between several servers presents many challenges, especially if those servers are at disparate networks across the world, and the connection between each has its own lag. Let me know what you're thoughts are on this.
|
Current version oh AHL supports the following types of setups:
1. Single server setup - when html and movies are served from the same box (right off the box)
2. Multiple server setup - when html on server "A" links to movies hosted on other domains or subdomains on servers "B" "C" ..., providing that those subdomians are hosted entirely on one server (there also needs to be a change to html pages done in this case)
3. DNS load balancing setup - when html and movies are hosted on multiple servers providing that user session is kept alive on one server with serves both html and movies
Load balancing setup with multiple servers described above by pancake7, will be supported by AHL Enterprise, scheduled to be released in a few weeks. It's already coded and is under testing on our stands.
