|
I know the subject of name-based HTTP load balancing isn't anything new, but
with the policy changes at ARIN:
http://www.arin.net/announcements/policy_changse.html
Webhosting providers who provide more than 256 hosts are being forced to use
name-based virtual hosts.
Now, of course, there are exceptions... SSL, FrontPage, FTP, etc. are going
to keep a great deal of web providers using IP-based technologies,
HOWEVER... ARIN's policy changes here call for a great deal of new
name-based technologies to develop.
So -- the need for name-based load balancing technologies suddenly became a
lot greater. Not only this, but new technologies are in development which
are going to help make various services (not only HTTP, but HTTPS, FTP,
etc.) available in a name-based form. Not only do I think that LVS
developers should take note of this, but perhaps help in the development in
these technologies.
Personally I:
* STRONGLY disagree with the ARIN policy changes (as you can see in some of
the ARIN groups to which I subscribe)
* Think that a new abstraction layer needs to be added to the IP model that
allows for a lower-level name-based paradigm to develop. That is -- right
now HTTP/1.1's ability to do name-based hosting allows ARIN to mandate that
it be used... but about every other protocol on the web as well as things
just made to improve HTTP does not support any sort of name-based
transactions. There is a need for this to allow for easy conversion to the
name-based world.
* Think that broadband Internet providers, like @Home and Time Warner, need
to be regulated... not webhosting providers -- but that's a completely
different discussion.
I just wanted to bring that up -- in case anyone didn't know or hadn't seen
what this means to LVS.
All the best --
Ted
|
