Slashdot Mirror

...when my cable ISP capped NNTP at 32kB/s because of the binary groups. That's all fine, because I usually use bittorrent or eDonkey for downloading files, but it has the side effect of making headers require several minutes to download in some of the larger groups. I'm sure this wouldn't help small groups, but it would surely take some of the load off of the NNTP server if a torrent-like system could be used to distribute the pages.

I've posted this before, but supposedly this company has technology to stream HTTP torrent-style. No idea if that's vaporware or what.

Swarmstreaming, I believe kids are calling it these days..:-P

These guys claim to have such a solution; I was just researching this stuff yesterday out of curiosity. Can't find any reviews or examples of people using it in order to determine if it actually works, though.

Here is some info on the new technology from the guy's company's website: http://onionnetworks.com/products/swarmstream/

On a sidenote, I seriously doubt that he is the very first one to have thought of swarming. Swarming has been around since before 1999 (when he claims he invented it). He *may* be the first one to have applied it to p2p/networking however.

http://onionnetworks.com/technology/swarming/#swar mstreaming

This sounds very useful, hopefully we will see these features adopted widely in the future

-dk

I'm proud to finally unveil swarmstreaming our third generation of swarming algorithms that are designed for the fastest downloads of web content and multimedia without any special server software or silly .swarm files. This is probably our most exciting advancement since the original invention of swarming.

The technology improves swarming by ensuring that the bytes that the user wants next are scheduled to be received next. So if they're playing back a video file, the bytes from the front of the file will be received first. If the user (or application) skips forward to the middle of the file, the bytes at the middle of the file will be prioritized. Thus, unlike first generation swarming systems like Swarmcast or Bittorrent, you don't have to wait for the entire file to download to do something useful with it!.

Under the covers it is almost unimaginably more complicated than this because it also provides Self-Healing Downloads, implements a full-blown, scalable, Web Proxy Cache, and actively works to ensure that the video playback never studders or buffers by constantly monitoring and adapting to changing network conditions. For a raw feature dump, check out the SwarmStream SDK Feature Matrix

Nowadays, because of its immense popularity, most people have only heard of swarming because of Bittorrent. I have no animosity towards Bittorrent because it has done more than any application to prove the value of swarming to the general public. But if people are impressed by Bittorrent, they're going to be absolutely blow away by swarmstreaming and how far we've taken swarming since its humble beginnings five years ago.

The best source of information right now on swarmstreaming is Onion Networks SwarmStream SDK, so check it out and let me know what you think.

I'm proud to finally unveil swarmstreaming our third generation of swarming algorithms that are designed for the fastest downloads of web content and multimedia without any special server software or silly .swarm files. This is probably our most exciting advancement since the original invention of swarming.

The technology improves swarming by ensuring that the bytes that the user wants next are scheduled to be received next. So if they're playing back a video file, the bytes from the front of the file will be received first. If the user (or application) skips forward to the middle of the file, the bytes at the middle of the file will be prioritized. Thus, unlike first generation swarming systems like Swarmcast or Bittorrent, you don't have to wait for the entire file to download to do something useful with it!.

Under the covers it is almost unimaginably more complicated than this because it also provides Self-Healing Downloads, implements a full-blown, scalable, Web Proxy Cache, and actively works to ensure that the video playback never studders or buffers by constantly monitoring and adapting to changing network conditions. For a raw feature dump, check out the SwarmStream SDK Feature Matrix

Nowadays, because of its immense popularity, most people have only heard of swarming because of Bittorrent. I have no animosity towards Bittorrent because it has done more than any application to prove the value of swarming to the general public. But if people are impressed by Bittorrent, they're going to be absolutely blow away by swarmstreaming and how far we've taken swarming since its humble beginnings five years ago.

The best source of information right now on swarmstreaming is Onion Networks SwarmStream SDK, so check it out and let me know what you think.

I'm proud to finally unveil swarmstreaming our third generation of swarming algorithms that are designed for the fastest downloads of web content and multimedia without any special server software or silly .swarm files. This is probably our most exciting advancement since the original invention of swarming.

The technology improves swarming by ensuring that the bytes that the user wants next are scheduled to be received next. So if they're playing back a video file, the bytes from the front of the file will be received first. If the user (or application) skips forward to the middle of the file, the bytes at the middle of the file will be prioritized. Thus, unlike first generation swarming systems like Swarmcast or Bittorrent, you don't have to wait for the entire file to download to do something useful with it!.

Under the covers it is almost unimaginably more complicated than this because it also provides Self-Healing Downloads, implements a full-blown, scalable, Web Proxy Cache, and actively works to ensure that the video playback never studders or buffers by constantly monitoring and adapting to changing network conditions. For a raw feature dump, check out the SwarmStream SDK Feature Matrix

Nowadays, because of its immense popularity, most people have only heard of swarming because of Bittorrent. I have no animosity towards Bittorrent because it has done more than any application to prove the value of swarming to the general public. But if people are impressed by Bittorrent, they're going to be absolutely blow away by swarmstreaming and how far we've taken swarming since its humble beginnings five years ago.

The best source of information right now on swarmstreaming is Onion Networks SwarmStream SDK, so check it out and let me know what you think.

I'm proud to finally unveil swarmstreaming our third generation of swarming algorithms that are designed for the fastest downloads of web content and multimedia without any special server software or silly .swarm files. This is probably our most exciting advancement since the original invention of swarming.

The technology improves swarming by ensuring that the bytes that the user wants next are scheduled to be received next. So if they're playing back a video file, the bytes from the front of the file will be received first. If the user (or application) skips forward to the middle of the file, the bytes at the middle of the file will be prioritized. Thus, unlike first generation swarming systems like Swarmcast or Bittorrent, you don't have to wait for the entire file to download to do something useful with it!.

Under the covers it is almost unimaginably more complicated than this because it also provides Self-Healing Downloads, implements a full-blown, scalable, Web Proxy Cache, and actively works to ensure that the video playback never studders or buffers by constantly monitoring and adapting to changing network conditions. For a raw feature dump, check out the SwarmStream SDK Feature Matrix

Nowadays, because of its immense popularity, most people have only heard of swarming because of Bittorrent. I have no animosity towards Bittorrent because it has done more than any application to prove the value of swarming to the general public. But if people are impressed by Bittorrent, they're going to be absolutely blow away by swarmstreaming and how far we've taken swarming since its humble beginnings five years ago.

The best source of information right now on swarmstreaming is Onion Networks SwarmStream SDK, so check it out and let me know what you think.

I'm proud to finally unveil swarmstreaming our third generation of swarming algorithms that are designed for the fastest downloads of web content and multimedia without any special server software or silly .swarm files. This is probably our most exciting advancement since the original invention of swarming.

The technology improves swarming by ensuring that the bytes that the user wants next are scheduled to be received next. So if they're playing back a video file, the bytes from the front of the file will be received first. If the user (or application) skips forward to the middle of the file, the bytes at the middle of the file will be prioritized. Thus, unlike first generation swarming systems like Swarmcast or Bittorrent, you don't have to wait for the entire file to download to do something useful with it!.

Under the covers it is almost unimaginably more complicated than this because it also provides Self-Healing Downloads, implements a full-blown, scalable, Web Proxy Cache, and actively works to ensure that the video playback never studders or buffers by constantly monitoring and adapting to changing network conditions. For a raw feature dump, check out the SwarmStream SDK Feature Matrix

Nowadays, because of its immense popularity, most people have only heard of swarming because of Bittorrent. I have no animosity towards Bittorrent because it has done more than any application to prove the value of swarming to the general public. But if people are impressed by Bittorrent, they're going to be absolutely blow away by swarmstreaming and how far we've taken swarming since its humble beginnings five years ago.

The best source of information right now on swarmstreaming is Onion Networks SwarmStream SDK, so check it out and let me know what you think.

I'm proud to finally unveil swarmstreaming our third generation of swarming algorithms that are designed for the fastest downloads of web content and multimedia without any special server software or silly .swarm files. This is probably our most exciting advancement since the original invention of swarming.

The technology improves swarming by ensuring that the bytes that the user wants next are scheduled to be received next. So if they're playing back a video file, the bytes from the front of the file will be received first. If the user (or application) skips forward to the middle of the file, the bytes at the middle of the file will be prioritized. Thus, unlike first generation swarming systems like Swarmcast or Bittorrent, you don't have to wait for the entire file to download to do something useful with it!.

Under the covers it is almost unimaginably more complicated than this because it also provides Self-Healing Downloads, implements a full-blown, scalable, Web Proxy Cache, and actively works to ensure that the video playback never studders or buffers by constantly monitoring and adapting to changing network conditions. For a raw feature dump, check out the SwarmStream SDK Feature Matrix

Nowadays, because of its immense popularity, most people have only heard of swarming because of Bittorrent. I have no animosity towards Bittorrent because it has done more than any application to prove the value of swarming to the general public. But if people are impressed by Bittorrent, they're going to be absolutely blow away by swarmstreaming and how far we've taken swarming since its humble beginnings five years ago.

The best source of information right now on swarmstreaming is Onion Networks SwarmStream SDK, so check it out and let me know what you think.

I'm proud to finally unveil swarmstreaming our third generation of swarming algorithms that are designed for the fastest downloads of web content and multimedia without any special server software or silly .swarm files. This is probably our most exciting advancement since the original invention of swarming.

The technology improves swarming by ensuring that the bytes that the user wants next are scheduled to be received next. So if they're playing back a video file, the bytes from the front of the file will be received first. If the user (or application) skips forward to the middle of the file, the bytes at the middle of the file will be prioritized. Thus, unlike first generation swarming systems like Swarmcast or Bittorrent, you don't have to wait for the entire file to download to do something useful with it!.

Under the covers it is almost unimaginably more complicated than this because it also provides Self-Healing Downloads, implements a full-blown, scalable, Web Proxy Cache, and actively works to ensure that the video playback never studders or buffers by constantly monitoring and adapting to changing network conditions. For a raw feature dump, check out the SwarmStream SDK Feature Matrix

Nowadays, because of its immense popularity, most people have only heard of swarming because of Bittorrent. I have no animosity towards Bittorrent because it has done more than any application to prove the value of swarming to the general public. But if people are impressed by Bittorrent, they're going to be absolutely blow away by swarmstreaming and how far we've taken swarming since its humble beginnings five years ago.

The best source of information right now on swarmstreaming is Onion Networks SwarmStream SDK, so check it out and let me know what you think.

I'm proud to finally unveil swarmstreaming our third generation of swarming algorithms that are designed for the fastest downloads of web content and multimedia without any special server software or silly .swarm files. This is probably our most exciting advancement since the original invention of swarming.

The technology improves swarming by ensuring that the bytes that the user wants next are scheduled to be received next. So if they're playing back a video file, the bytes from the front of the file will be received first. If the user (or application) skips forward to the middle of the file, the bytes at the middle of the file will be prioritized. Thus, unlike first generation swarming systems like Swarmcast or Bittorrent, you don't have to wait for the entire file to download to do something useful with it!.

Under the covers it is almost unimaginably more complicated than this because it also provides Self-Healing Downloads, implements a full-blown, scalable, Web Proxy Cache, and actively works to ensure that the video playback never studders or buffers by constantly monitoring and adapting to changing network conditions. For a raw feature dump, check out the SwarmStream SDK Feature Matrix

Nowadays, because of its immense popularity, most people have only heard of swarming because of Bittorrent. I have no animosity towards Bittorrent because it has done more than any application to prove the value of swarming to the general public. But if people are impressed by Bittorrent, they're going to be absolutely blow away by swarmstreaming and how far we've taken swarming since its humble beginnings five years ago.

The best source of information right now on swarmstreaming is Onion Networks SwarmStream SDK, so check it out and let me know what you think.

I'm proud to finally unveil swarmstreaming our third generation of swarming algorithms that are designed for the fastest downloads of web content and multimedia without any special server software or silly .swarm files. This is probably our most exciting advancement since the original invention of swarming.

The technology improves swarming by ensuring that the bytes that the user wants next are scheduled to be received next. So if they're playing back a video file, the bytes from the front of the file will be received first. If the user (or application) skips forward to the middle of the file, the bytes at the middle of the file will be prioritized. Thus, unlike first generation swarming systems like Swarmcast or Bittorrent, you don't have to wait for the entire file to download to do something useful with it!.

Under the covers it is almost unimaginably more complicated than this because it also provides Self-Healing Downloads, implements a full-blown, scalable, Web Proxy Cache, and actively works to ensure that the video playback never studders or buffers by constantly monitoring and adapting to changing network conditions. For a raw feature dump, check out the SwarmStream SDK Feature Matrix

Nowadays, because of its immense popularity, most people have only heard of swarming because of Bittorrent. I have no animosity towards Bittorrent because it has done more than any application to prove the value of swarming to the general public. But if people are impressed by Bittorrent, they're going to be absolutely blow away by swarmstreaming and how far we've taken swarming since its humble beginnings five years ago.

The best source of information right now on swarmstreaming is Onion Networks SwarmStream SDK, so check it out and let me know what you think.

I'm proud to finally unveil swarmstreaming our third generation of swarming algorithms that are designed for the fastest downloads of web content and multimedia without any special server software or silly .swarm files. This is probably our most exciting advancement since the original invention of swarming.

The technology improves swarming by ensuring that the bytes that the user wants next are scheduled to be received next. So if they're playing back a video file, the bytes from the front of the file will be received first. If the user (or application) skips forward to the middle of the file, the bytes at the middle of the file will be prioritized. Thus, unlike first generation swarming systems like Swarmcast or Bittorrent, you don't have to wait for the entire file to download to do something useful with it!.

Under the covers it is almost unimaginably more complicated than this because it also provides Self-Healing Downloads, implements a full-blown, scalable, Web Proxy Cache, and actively works to ensure that the video playback never studders or buffers by constantly monitoring and adapting to changing network conditions. For a raw feature dump, check out the SwarmStream SDK Feature Matrix

Nowadays, because of its immense popularity, most people have only heard of swarming because of Bittorrent. I have no animosity towards Bittorrent because it has done more than any application to prove the value of swarming to the general public. But if people are impressed by Bittorrent, they're going to be absolutely blow away by swarmstreaming and how far we've taken swarming since its humble beginnings five years ago.

The best source of information right now on swarmstreaming is Onion Networks SwarmStream SDK, so check it out and let me know what you think.

Swarmstreaming: Swarming Downloads Evolved
I'm proud to finally unveil swarmstreaming our third generation of swarming algorithms that are designed for the fastest downloads of web content and multimedia without any special server software or silly .swarm files. This is probably our most exciting advancement since the original invention of swarming.

The technology improves swarming by ensuring that the bytes that the user wants next are scheduled to be received next. So if they're playing back a video file, the bytes from the front of the file will be received first. If the user (or application) skips forward to the middle of the file, the bytes at the middle of the file will be prioritized. Thus, unlike first generation swarming systems like Swarmcast or Bittorrent, you don't have to wait for the entire file to download to do something useful with it!.

Under the covers it is almost unimaginably more complicated than this because it also provides Self-Healing Downloads, implements a full-blown, scalable, Web Proxy Cache, and actively works to ensure that the video playback never studders or buffers by constantly monitoring and adapting to changing network conditions. For a raw feature dump, check out the SwarmStream SDK Feature Matrix

Nowadays, because of its immense popularity, most people have only heard of swarming because of Bittorrent. I have no animosity towards Bittorrent because it has done more than any application to prove the value of swarming to the general public. But if people are impressed by Bittorrent, they're going to be absolutely blow away by swarmstreaming and how far we've taken swarming since its humble beginnings five years ago.

The best source of information right now on swarmstreaming is Onion Networks SwarmStream SDK, so check it out and let me know what you think.

He links to http://onionnetworks.com/technology/swarming/#swar mstreaming

Here's a link to Onion Networks' Swarmstream product. It appears that to use the product, you need to purchase a Swamstream SDK, though.

Related to this, check out the Visual P2P/Swarming Simulation.

It allows you to visualize firewalled transfers.

He is one of my employees at Onion Networks and is an insanely talented developer. His web site is at http://ry4an.org/unblog/

Hopefully he'll get on this thread and respond with his experiences.

Basically, you click on a link which will subscribe the peer to the channel, and the peer will automatically download/pre-cache any new items that are added to the RSS feed.

You simply have to create an RSS feed and create a link that converts that feed into a channel that is subscribable via the Open Content Network. I've set up an example of a movie trailer RSS feed here And have linked it into the Open Content Network here.

Basically, you click on a link which will subscribe the peer to the channel, and the peer will automatically download/pre-cache any new items that are added to the RSS feed.

You simply have to create an RSS feed and create a link that converts that feed into a channel that is subscribable via the Open Content Network. I've set up an example of a movie trailer RSS feed here And have linked it into the Open Content Network here.

I run a software company called Onion Networks that provides peer-to-peer content delivery technology to movie studios building VOD systems.

With fast P2P content delivery technology, MPEG-4 compression, and PVR-like time shifting devices - the speed, storage, and economics are there today to provide DVD-quality VOD.

The only problem is that it is taking the studios a long time to roll out there VOD solutions, but trust me, they'll be upon us in the near future.

For more information on the protocols that underly these P2P content delivery systems, please check out the Open Content Network Specs

The most up to date version of the Java FEC library can be found here.

The most up to date version of the Java FEC library can be found here.

If you look at how it works, there is no other way to pull this off besides using a browser plugin. Of course, this could be integrated into the browser, but that hasn't happened yet.

If your being sarcastic with the distro comment: You may note that the article says nothing of getting the latest distros, but making redundant mirrors on a P2P network of sites that get overloaded or /.'d.

The other thing is I don't understand how they can prevent people from using this for illegal files. Anyone can enable their website to support this type of downloading and there is no central moderation. People were screaming "READ THE ARTICLE" at one guy who posed the question of illegal files, but as you can see, it's really quite simple to slap that JavaScript code on any page reguardless of if it has an OSI-approved license. OCN isn't meant for divx or warez, but it wouldn't be hard to make it that way; I see no way of preventing this.

[sarcasm]Oh, and by "gay" you mean this plug-in is happy? Because using that as a derogatory term really makes your case stronger with another dumb reply.[/sarcasm]

To me, it looks like this system can sort of do that. Point people to your little web server and add a few lines of Javascript to the top of your main web page and all the files reached from there, with extensions that you specify, will be served via the P2P cache. See the instructions. Also on that page is a link to a large PDF which gets served P2P via an OnionNetworks Java applet. The PDF loaded for me in about 20 seconds. A disadvantage for the user is that currently PDF's stream and you instantly see the first page.

Perhaps Slashdot could use this only in certain cases like when linking to a pdf or linking directly to the newest iso.

a fully distributed content-addressible web
infrastructure is the best way to resolve this
problem once and for all. linked with a
good distributed proxy infrastructure, or better yet, a fully anonymized transport it will take herculean efforts
to do this kind of information-suppression.

Freenet already has this feature. Large files are split into 256KB chunks and they can optionally be encoded with extra redundancy using FEC, so one does not have to download all chunks of the file to get the complete file.

We wrote an optimized Reed-Solomon library for Swarmcast that can do up to 65k shares. Its available under a BSD-style license. Also, since Swarmcast is a P2P content delivery system, the library also supports cryptographic integrity checking, so you can ensure that everything is in tact.

Unfortunately the Swarmcast project has languished after 1.0, but we have started a new project called the "Open Content Network"

The Content-Addressable Web provides HTTP extensions that solve many of the problems associated with distributing content across ad hoc networks. This is because the addressing of the system is location-independant and content-centric. This makes it perfect for unreliable and transient wireless networks.

--
Justin Chapweske, Onion Networks

The Content-Addressable Web provides HTTP extensions that solve many of the problems associated with distributing content across ad hoc networks. This is because the addressing of the system is location-independant and content-centric. This makes it perfect for unreliable and transient wireless networks.

--
Justin Chapweske, Onion Networks

If code is in the public domain anyone is free to do whatever they want with it. Therefore it is by definition Open Source. I'm sure if you check out the OSD on opensource.org it will include Public Domain.

--
Justin Chapweske, Onion Networks

It would be really cool if the Redhat Network supported the Content-Addressable Web so that we could automatically download our ISOs from the closests avaliable mirrors, and even download from multiple mirrors in parallel.

Stay tuned for the O'Reilly Emerging Technology Conference where we will be unveiling a companion set of technologies to the CAW that will change distribution of open source content forever!

If anyone wants to know more about CAW before the conference, please contact me at justin_at_onionnetworks_dot_com

--
Justin Chapweske, Onion Networks

It would be really cool if the Redhat Network supported the Content-Addressable Web so that we could automatically download our ISOs from the closests avaliable mirrors, and even download from multiple mirrors in parallel.

Stay tuned for the O'Reilly Emerging Technology Conference where we will be unveiling a companion set of technologies to the CAW that will change distribution of open source content forever!

If anyone wants to know more about CAW before the conference, please contact me at justin_at_onionnetworks_dot_com

--
Justin Chapweske, Onion Networks

We're working on it, something will probably be ready in time for the O'Reilly Emerging Technologies conference.

--
Justin Chapweske, Onion Networks

We did a significant amount of work in this vein with Swarmcast and have been building a lot of the (rather complex) technology necessary for Reliable Multicast

Multicast is not panacea though, because it is not very widely deployed on the Internet, and since there is no caching in Multicast, all of the receivers must be downloading near the same time to realize the bandwidth savings...So in many ways P2P caching has advantages over multicast, which is why we do both.
--
Justin Chapweske, Onion Networks

We did a significant amount of work in this vein with Swarmcast and have been building a lot of the (rather complex) technology necessary for Reliable Multicast

Multicast is not panacea though, because it is not very widely deployed on the Internet, and since there is no caching in Multicast, all of the receivers must be downloading near the same time to realize the bandwidth savings...So in many ways P2P caching has advantages over multicast, which is why we do both.
--
Justin Chapweske, Onion Networks

Jibe has a wonderful product for enterprise file and data sharing and I think is making some good progress and will be quite successful.

My employer, Onion Networks, is focused on building enterprise content delivery solutions using P2P. 2002 is off to a great start for us as companies are immediately seeing the value of P2P for cutting costs and increasing reliability within their networks.

--
Justin Chapweske, Onion Networks

Jibe has a wonderful product for enterprise file and data sharing and I think is making some good progress and will be quite successful.

My employer, Onion Networks, is focused on building enterprise content delivery solutions using P2P. 2002 is off to a great start for us as companies are immediately seeing the value of P2P for cutting costs and increasing reliability within their networks.

--
Justin Chapweske, Onion Networks

With the Content-Addressable Web standard, we have built secure hashes into the very fabric of the network. CAW goes so far as to use them to provide a uniform URI for a unique piece of content, regardless of its location on the network.

--
Justin Chapweske, Onion Networks

With the Content-Addressable Web standard, we have built secure hashes into the very fabric of the network. CAW goes so far as to use them to provide a uniform URI for a unique piece of content, regardless of its location on the network.

--
Justin Chapweske, Onion Networks

Oh yeah, and you can download our completely patent-free and open source FEC library from here and build your own Multicast or UDP based download system very quickly (provided you get the flow control right :)

--
Justin Chapweske, Onion Networks

Oh yeah, and you can download our completely patent-free and open source FEC library from here and build your own Multicast or UDP based download system very quickly (provided you get the flow control right :)

--
Justin Chapweske, Onion Networks

The "Math" they use is called Forward Error Correction (FEC) and is the same stuff that the Swarmcast distributed download system is based off of (http://sf.net/projects/swarmcast/).

I am the creator of Swarmcast, and we at Onion Networks (http://onionnetworks.com/) already have a product that can provide file transfers just as fast as Digital Fountain, but ours is 3-5.5% more efficient and much much cheaper.

On the open source front, we are working on the next generation of the Swarmcast technology which will combine parallel downloads over HTTP, Multicast IP, and UDP (for tunnelling through NAT). We have started work defining a standard for this system called the "Content-Addressable Web" and hope to see it implemented in everything from Apache to Mozilla.

Please mod this up, people shouldn't be paying $150k for these types of technologies.

The "Math" they use is called Forward Error Correction (FEC) and is the same stuff that the Swarmcast distributed download system is based off of (http://sf.net/projects/swarmcast/).

I am the creator of Swarmcast, and we at Onion Networks (http://onionnetworks.com/) already have a product that can provide file transfers just as fast as Digital Fountain, but ours is 3-5.5% more efficient and much much cheaper.

On the open source front, we are working on the next generation of the Swarmcast technology which will combine parallel downloads over HTTP, Multicast IP, and UDP (for tunnelling through NAT). We have started work defining a standard for this system called the "Content-Addressable Web" and hope to see it implemented in everything from Apache to Mozilla.

Please mod this up, people shouldn't be paying $150k for these types of technologies.

The company's name is OpenCola and the name of the product was SwarmCast. The guy who did SwarmCast, Justin Chapewske, is now at a company he started named Onion Networks. OpenCola appears to have completely abandon its original Open Source approach to their software.

Apparently, Justin has taken the GPL portions of Swarmcast and is improving them at Onion Networks.

The company which did that was openCola with a OpenSource product called Swarmcast, but as far as I know they have abandoned the project and cut of the developers off their payroll. However they are still going on at sourceforge.

I know few of the developers and one of them has started a service company, selling services for swarmcast called Onion Networks

AK

The Content-Addressable Web provides all of the asked-for features, including multi-source/parallel downloads, and the ability to safely retrieve content from untrusted mirrors.

Please read the paper and tell me what you think.

The cornerstone technology to any reliable multicast system is FEC (Forward Error Correction) which is an encoding technique that can repair lost or corrupt packets.

We at Onion Networks have created a very solid FEC library that will form the foundation of our open source implementations of the reliable multicast protocols. The FEC library can be had at http://onionnetworks.com/components.html

Hi, I am Justin Chapweske, the inventor of OpenCola's Swarmcast. I am now working on another software project to specifically address the needs of content distribution over multicast, and the Onion Networks FEC Library is the first step in building that soluiton. The FEC library will provide the foundation of our future open source multicast content distribution software, so keep an eye out at http://onionnetworks.com for more info.

Hi, I am Justin Chapweske, the inventor of OpenCola's Swarmcast. I am now working on another software project to specifically address the needs of content distribution over multicast, and the Onion Networks FEC Library is the first step in building that soluiton. The FEC library will provide the foundation of our future open source multicast content distribution software, so keep an eye out at http://onionnetworks.com for more info.