> On 2008.03.17, Russ Nelson <[EMAIL PROTECTED]> wrote: >> Well, but when you're streaming through a TCP connection, you cannot >> guarantee at the beginning that every block will be available by the >> time you're ready to consume it. > > True. > >> The biggest difference between TCP and BitTorrent is that TCP delivers >> data in the same order you sent it, which is the order in which the >> user wants it, whereas BitTorrent delivers in random order, so you >> potentially have to wait until the very end of reception. Then again, >> people's typical response to insufficient bandwidth (slow delivery) is >> to click on pause until the entire stream has been received. > > Given that BitTorrent streaming isn't practical, is there real value in > tightly integrating Gnash with a BitTorrent client? It seems like a lot > of work for very little return, IMHO.
Joost works fine with it's P2P technique! And only using P2P makes it possible to broadcast huge amounts of multimedia data. Just consider if you want to broadcast a movie with 2 MBit/s to 100,000 users - thats 200,000 MBit/s upstream traffic! Using P2P you need only 2 MBit/s plus some 100 MBit/s to compensate latencies or blocks which aren't available in the swarm anmore. Have Phun, Renne _______________________________________________ Gnash-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-dev
