WEBTORRENT STABLE RELEASE TORRENT

Interpret pieceIndex as an identifier.More concretely, here are my proposed modifications to WebTorrent to support live delivery: If we reinterpret that number as a piece identifier (and relax some constraints about piece density), existing peer behavior starts looking applicable to a lot more scenarios. From the perspective of the peer protocol, however, a piece index is just a number. Torrents created from the traditional metadata assign piece indices sequentially based on file declaration order. Requests specify a piece index, a byte offset, and a length. Peers distribute content by exchanging request and piece messages in the peer protocol. Just like WebTorrent, it’s probably necessary for some client changes but to keep them to an absolute minimum. The idea here is similar: use the best parts of the BitTorrent and live streaming ecosystem so that it’s easy for existing, battle-tested clients and tools to adopt. WebTorrent uses the BitTorrent protocol because it’s already proven and hugely successful. The goal of this proposal is to enhance conventional live streaming with P2P. WebTorrent could flip that on its head and make live streaming more reliable as audiences surge. Live events are unpredictable and traditional scaling mechanisms aren’t designed for usage to spike by a factor of a million in the span of a few minutes. Live streaming could benefit enormously from a robust peer-assisted model. Workarounds exist ( “Is it possible to do live streaming with WebTorrent?”, for instance) but they have substantial drawbacks – torrents are either at a signficant delay or the timeframe for peers to assist in delivery is very limited.

That makes BitTorrent (and consequently, WebTorrent) difficult to use with live media.

WEBTORRENT STABLE RELEASE TORRENT

The BitTorrent protocol assumes that files in a torrent are known ahead of time.

Webtorrent stable release