|
|
Posted by Joel Shepherd on 10/29/05 21:16
In article <YqI8f.19110$6i4.17621@newsfe7-gui.ntli.net>,
Stuart <stuart@edesign.cc> wrote:
> Per Jψrgen Vigdal wrote:
> > A plain old hypertext does not solve my problem.
> >
> > Because I do not think it is a good solution to
> > ask the user to hit one link(URL_A), and explain that if it does not work
> > Go back and hit another.( URL_B)
>
> True, but the only other viable way is to use server-side scripting
> (PHP, ASP etc).
No: there are server-side hardware solutions as well. Setting up a
hardware load-balancer with a virtual IP address over a pool of
webservers will generally assure that clients are directed to 'live'
webservers. (Of course if a live webserver goes down in the middle of
handling a request, that request is out of luck, but ...).
<http://www.cisco.com/univercd/cc/td/doc/product/iaabu/localdir/ld31rns/l
dicgd/ld3_ch1.htm>
Sound like overkill? For the vast majority of sites it is. For most of
us mortals, having the webserver go down for a little while is an
annoyance, but not worth a significant investment in network hardware to
avoid. But if the OP is looking to do it right, a hardware load-balancer
is the most reliable way of assuring that requests get routed to a live
server.
--
Joel.
[Back to original message]
|