Coral P2P Cache Enters Public Beta
Eloquence writes "infoAnarchy reports that Coral, a peer-to-peer webcaching system, has gone into public beta. Currently the Coral node network is hosted on Planet-Lab, a large scale distributed research network of 400 servers. You can use Coral right now by appending "nyud.net:8090" to a hostname. View Slashdot through Coral. Is this the end of the Slashdot effect?"
Google cache has been a good helper to me for some time.
So this is not so new to me regarding slashdot effects.
Notice that because of the caching system it isn't fully current...
Windows: Linux: Seems their nameservers have some kind of problem. I am in the Midwest, going through an AT&T OC3 (everything else works fine from here; it's not a local problem). It works OK when I check from our California-based servers that peer with Mae West, however.
links should be (and usually are) relative, eg:
img src="img/logo.png"
not:
img src="http://slashdot.org/img/logo.png"
or whatever so this shouldn't be a problem
Marge, get me your address book, 4 beers, and my conversation hat.
http://www.archive.org/web/freecache.php
It isn't P2P web proxy, it's just "big pipe"-based distributed one. Supposedly a great way to prevent slashdoting (just use http://freecache.org/http://mytinysite.com instead of http://mytinysite.com and everything goes from the cache, tiny site receiving only header requests to chceck if the document hasn't changed in the meantime) it's hardly known, way too quiet as for a project that useful. P2P may be faster and cheaper but certainly less reliable...
45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
Here.
http://www.scs.cs.nyu.edu/coral/stats/
Doesn't it analyze hyperlinks?
All the links on Slashdot have the format
<a href="//slashdot.org/blahblahblah">
so that they will always link back to Slashdot. Most websites just use "blahblahblah" or "/blahblahblah" for their links. For example, links on google.com.nyud.net are fully functional.
The problem is that it doesn't seem to be compatible with Microsoft DNS severs. Below is a copy of the DNS log when I issue a query here, on my LAN which has a Microsoft DNS server running on Windows 2000, which then forwards through the University of Wisconsin. You can see that at the end it says "The DNS server encountered an invalid domain name." Perhaps someone who knows more about DNS can tell where the problem is?
It's not p2p.
It's 'distributed'.
Peer to peer implies that the users of the service are the ones supporting it's existance.
so that they will always link back to Slashdot. Most websites just use "blahblahblah" or "/blahblahblah" for their links. For example, links on
Well...all they have to do is have some modifying code like CGI-Proxy does....
Show me on the doll where his noodly appendage touched you.
As far as I know, anybody in the 0.5gig/month or over (all the way up to the backbone carrierers, which have to have peering agreements as an exception to the rule of charging for bandwidth) charges per megabyte.
Sounds like we need a little lesson on How cookies work.
.apple.com can interact with any Apple subdomain.
/., or any other cookies.
To summarize it, though, they're set on a per-domain basis.
www.apple.com can set a cookie.
store.apple.com can set a cookie.
The two cannot interact with each other; however,
microsoft.com cannot access any of your apple.com cookies.
Thus, nyud.net cannot access your
"An infinite number of monkeys typing into GNU emacs would never make a good program."
Here, I'll even link you to a good client that will give you a nice GUI for starting out. Another Bittorent Client for all OSes.
SAILING MISHAP
Check out their logs...
...note the recent blip?
Coral Statistics
Maw! Fire up the karma burner!
I have to believe that ISPs that provide web services would find their revenue reduced since they would not see all the hits on the site.
It seems you're confusing a "cache" with a "proxy." A "cache" is only DESIGNED to work on static pages, and it doesn't hit the page more than once (barring refreshing). That's what "cache" means. The pages are stored on the cache server and fed to the clients as they get requested, cutting down on hits to the actual site.
The above link from an anonymous coward points to a paper through some weird obfuscation that does just that. HTTP(P2P)