# > round robin DNS spreads the load but not evenly (of course neither does
# > this simple version) but the idea of being able to direct traffic to a
# > particular server based on the URL has all sorts of possibilities.
#
# Its also old hat. The front server just needs to run apache and the mod
# rewrite stuff to generate a page back which is a redirect to the real
# site for those pages.
But that isn't efficient in the slightest. From a simple
request->response, you've created a request->redirect->request->response
chain. Add the possibility of the redirect being to a different host and
you can add a slow DNS lookup in the middle of the chain. And if you do
this all transparent to your page authors, then add the potential for a
graphic ladden page to be getting redirects for everything it loads.
I've seen crap like this in action and its scary. Modperl+apache !=
efficient load balancing.
Now, if you could actually hand off the network connection to another box,
without having to send any client-bound messages, that would be cool.
Hmm....
G'day!
-----------------------------------------------------------------------------
Nicholas J. Leon "Elegance Through Simplicity"
nicholas@binary9.net - - http://mrnick.binary9.net
8 4 9 1 7 3 <-- what is the pattern?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html