W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1996

RE: multi-host virtual sites for HTTP 1.2

From: Paul Leach <paulle@microsoft.com>
Date: Tue, 9 Jul 1996 16:08:18 -0700
Message-Id: <c=US%a=_%p=msft%l=RED-77-MSG-960709230818Z-17719@abash1.microsoft.com>
To: "'http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com'" <http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com>, "'S.Venkatramanan@Eng.Sun.COM'" <S.Venkatramanan@eng.sun.com>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/1064

>From: 	S.Venkatramanan@Eng.Sun.COM[SMTP:S.Venkatramanan@Eng.Sun.COM]
>Subject: 	Re: multi-host virtual sites for HTTP 1.2
>> From http-wg-request@cuckoo.hpl.hp.com Tue Jul  9 15:24 PDT 1996
>> With the Host: header in HTTP/1.1 it is possible to efficiently and
>> easily make a single host act as many "virtual" Web sites.
>> What I'd like to see in HTTP/1.2 is the ability to easily and
>> efficiently make multiple hosts act like a single virtual Web site, so
>> that one can build huge web sites.
>I think this is just an implementation, or rather, a site
>problem than a protocol defeciency.  How about using a round-robin DNS
>to map the hostname to multiple irons, use the power of such multiple
>hosts in the cluster to serve nfs mounted files from the same or similar
>This will not necessitate redirection with Location: header;  the name
>megasoft.com becomes virtual and need not be heavily loaded; the contents
>need not be replicated as they are all NFS mounted and hence distributed
>in the network (may be high speed because they are all potentially
>May be there are some other issues I am missing in this simpleton approach.

You're right that this scales. But the proposal from my original mail
should be quite a bit more efficient, because in your suggestion every
request gets handled by two hosts instead of one, and all content makes
three trips through a network controller instead of one. For the same
reasons, latency is better when the request goes straight to the host
that has the resource.

In addition, there are issues when updates are allowed. I didn't point
this out in my original mail, but when the hosts are individually named,
a request that does an update can quite easily be redirected to the
"master" which processes all updates.

Received on Tuesday, 9 July 1996 16:24:07 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:17 UTC