Coral Content Distribution Network Information & Coral Content Distribution Network Links at HealthHaven.com
advertise
add site
services
publishers
database
health videos
Bookmark and Share

search wiki for    ?
web dir firms image gallery news pdf wiki shop video 
about
toolbar
stats
live show
health store
more stuff
JOIN/LOGIN
Featured Results:
- Avnet Abacus Signs Pan-European Distribution Agreement with...
- Avnet Abacus Signs Pan-European Distribution Agreement with...
medicaldevice-network.com
 Strengthens Its Polarized Network Distribution , Announces Acquisition...
Strengthens Its Polarized Network Distribution, Announces Acquisition...
ecpmag.com
  Distribution network of Biotechdesk suppliers/dealers of research...
Distribution network of Biotechdesk suppliers/dealers of research...
biotechdesk.com
 
Coral Content Distribution Network
Coral CDN logo.png
Developer(s) Link
Operating system Cross-platform (web-based application)
Type P2P Web cache
Website www.coralcdn.org

The Coral Content Distribution Network, sometimes called Coral Cache or Coral, is a free peer-to-peer content distribution network designed and operated by Michael Freedman. Coral uses the bandwidth of volunteers to mirror web content, often to avoid the Slashdot Effect or to reduce the load on websites in general.

Contents

[edit] Operation

One of Coral's key goals is to avoid ever creating 'hot spots' of very high traffic, as these might dissuade volunteers from running the software out of a fear that spikes in server load may occur. It achieves this through an indexing abstraction called a distributed sloppy hash table (DSHT); DSHTs create self-organizing clusters of nodes that fetch information from each other to avoid communicating with more distant or heavily-loaded servers.

The sloppy hash table refers to the fact that coral is made up of concentric rings of distributed hash tables (DHTs), each ring representing a wider and wider geographic range (or rather, ping range). The DHTs are composed of nodes all within some latency of each other (for example, a ring of nodes within 20 milliseconds of each other). It avoids hot spots (the 'sloppy' part) by only continuing to query progressively larger sized rings if they are not overburdened. In other words, if the two top-most rings rings are experiencing too much traffic, a node will just ping closer ones: when a node that is overloaded is reached, upward progression stops. This minimises the occurrence of hot spots, with the disadvantage that knowledge of the system as a whole is reduced.

Requests from users are directed to a relatively close node, which then finds the file on the coral DSHT and forwards it to the user.

[edit] Usage

A website can be accessed through the Coral Cache by adding .nyud.net to the hostname in the site's URL, resulting in what is known as a 'coralized link'. So, for example, http://example.com becomes http://example.com.nyud.net. For websites that use a non-standard port for example, http://example.com:8080 becomes http://example.com.8080.nyud.net.

[edit] History

The project has been deployed since March 2004, during which it has been hosted on PlanetLab, a large scale distributed research network of several hundred servers deployed at universities world wide. It has not, as originally intended, been deployed by third party volunteer systems. About 300-400 PlanetLab servers are currently running CoralCDN. The source code is freely available under the terms of the GNU GPL.

Coral Cache gained widespread recognition in the aftermath of the 2004 Indian Ocean earthquake, when it was used to allow access to otherwise inaccessible videos of the resulting tsunami.[citation needed]

[edit] Problems

Some web filtering software packages, such as Websense and OpenDNS, block access to the Coral Cache as it is seen as a form of proxy avoidance.

[edit] See also

[edit] External links




Product Results (view all...)

search wiki for    ?
web dir firms image gallery news pdf wiki shop video 



↑ top of page ↑about thumbshots