Slashdot Mirror
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?"
you can ensure that your readers can still access a certain web page or files, when the multitude of readers would otherwise overload the website and make the content unavailable.
well apparently all html content, including files, will be cached. this is a great way to get around downloading from snail-pace sites, (although i will be checking md5sums)
Marge, get me your address book, 4 beers, and my conversation hat.
Is there any way to force firefox to append the p2p information automatically so we browse the cache all the time instead of the normal websites?
as will ISPs if it takes off. Right now with bandwidth usage centralized it's pretty easy to bill for it. If you decentralize it with p2p via millions of always on unmetered clients/servers it gets hard, if not impossible. I kinda hope it doesn't take off, since if it does it could end unmetered Internet access...
Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
This would also by pass any restricted sites your company may be blocking...
This is a Content Distributon network of cooperating servers colloborating to exchange information and 'level out' excess demand by distributing reqiests among n servers. Like Akamai's EdgeSuite. based on a quick read of the front page. The providors of content in their network are never the consumers if content. thus i don't know why they call it peer-to-peer? anyone?
Some reason, this works but this doesn't... guess there are limits to recursion. If for some reason the last link works, keep adding nyud.nets...
It's turtles all the way down...
I love the idea. I hope that it doesn't have as much trouble being functional as projects like freenet.
http://slashdot.org.nyud.net:8090/ caches only the /. homepage. Doesn't it analyze hyperlinks?
Goatse-links trolls will be back, with slashcode showing the same domain for every link, I think CmdrTaco has some work to do now.
The IT section color scheme sucks.
Try starting with "ma" instead of "mo" ;)
I can understand back in the day where a 300MHz computer was expensive; and I can understand why a 128K hosted-at-home site won't survive one. But c'mon, guys - in this day of fast CPUs and cheap bandwidth, how can your servers _not_ handle a few more users. Is everyone using .NET or Java bloat to make up for the advances in hardware over the years?
PS: Yes, i've survived a slashdotting, with 300MHz sparcs. No, it wasn't a big deal. A much bigger event was a nationwide radio show that had its peak traffic concentrated over 2-5 minutes, unlike /.'s gradual half-hour of increased traffic. The Howard Stern effect (if he mentiones sex) and the National Public Radio effect (if its an interesting story) each put the /. effect to shame over 1-minute timeframes.
Although I agree with others, it doesn't really compare to FreeCache. I still wonder why that never got much attention. It's an insanely great idea. Ah well. Between that, Corla, and BitTorrent, you never have to worry about /.'ing again when you submit your tiny personal site.
In other news (for the morons who continue posting and whining), you can still remove the it prefix from the /. URL, removing the fugly colour scheme. And there was much rejoicing in the land.
(-:Stephonovich:-)
"Who needs reincarnation when we've got parallel universes?" -Me
I haven't checked the terms of use to see if I'm allowed to use this for my work web site, though maybe with a cash or hardware donation, or by running a high-bandwidth node, I can get permission.
What I'm thinking is that at work I run a multi-server site that gets massively bogged down for short periods when it tries to handle upwards of 35,000 concurrent sessions. Bandwidth is not the problem, the application is, and it can't be rewritten for reasons that piss me off and I have no budget for more servers and no management support to run a static cached version of the site.
So I was wondering if it was possible to have the site automatically direct visitors to the Coralized URL when the site load gets too high. Either a manual change or an automatic one would be ok. I have some ideas on how this could be done using a failover server config on our ServerIron. Possibly a router config can also do this, though we don't run our own router since it's at a colocation facility. Worst case scenario is I can edit the home page to redirect to Coral when the load gets high.
Are there any other Slashdotters looking to use Coral in similar ways? If you have any ideas to share I'd be all ears.
The global economy is a great thing until you feel it locally.
It might sound better if you wrote " moddo appu onegai". The pronoun "me" made it sound awkward to me. It would sound fine in English without the pronoun (e.g. "mod up please"), and since the Japanese dislike pronouns in the first place, you might as well take it out. Plus, without the pronoun it sounds like more traditional katakana usage rather than forced English.
:)
I'm not a native speaker though, so ymmv.
Try something like:e t.nyud.net.nyud.net.nyud.net.nyud.net.nyud.net.nyu d.net.nyud.net.nyud.net:8090/
http://nyud.net.nyud.net.nyud.net.nyud.net.nyud.n
The practice of allowing portnumbers seems dangerous. I can imagine links like http://localhost.19.nyud.net:8090/ or http://loghost.515.nyud.net:8090/ being used for nefarious purposes.
Regards,
--
*Art