Date: Wed, 30 Jan 2002 00:29:10 +0100 From: devet@devet.org (Arjan de Vet) To: brad.knowles@skynet.be Cc: chat@freebsd.org Subject: Re: serving content from the closest server Message-ID: <20020129232909.GA1942@adv.devet.org> In-Reply-To: <p0510120bb87cc4d04e2c@[10.0.1.21]> References: <Pine.LNX.4.43.0201291249530.14819-100000@pilchuck.reedmedia.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <p0510120bb87cc4d04e2c@[10.0.1.21]> you write: > Well, there's the Akamai solution -- have the content provider >use an Akamai-specific URL, which points at an Akamai server. When >the URL is accessed, proprietary algorithms are used by Akamai to >determine the geographic and topological location of the user, and >the "nearest" Akamai server, at which point a redirect is issued to >that local server. When the request hits the local server, it serves >up the content from its local cache, or pulls the content from the >private source location and and then caches this as well as passing >it on to the requester. Last time I looked at the Akamai setup their DNS servers handed out different IP addresses for the same hostname depending on the source of the DNS request in order to redirect people to the nearest Akamai server. So no HTTP redirects at all AFAIK. I remember checking this because of a (probably Dutch) conference paper describing a.o. the Akamai setup. Arjan -- Arjan de Vet, Eindhoven, The Netherlands <devet@devet.org> URL : http://www.iae.nl/users/devet/ <Arjan.deVet@adv.iae.nl> Work: http://www.madison-gurkha.com/ (Security, Open Source, Education) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020129232909.GA1942>