diff options
author | Feross Aboukhadijeh <feross@feross.org> | 2015-01-16 10:36:21 +0300 |
---|---|---|
committer | Feross Aboukhadijeh <feross@feross.org> | 2015-01-16 10:36:32 +0300 |
commit | d880b81ff83a860594a5310dd0a05fdb1ca7f876 (patch) | |
tree | 396690494d460ed5dc5be56d7ccef9bf9bc2963c | |
parent | 4ef0761c238a5eae6d189c55dc6d460da52a8cb5 (diff) |
readme
-rw-r--r-- | README.md | 11 |
1 files changed, 6 insertions, 5 deletions
@@ -13,9 +13,8 @@ THAT'S RIGHT. THE BROWSER. It's written completely in JavaScript – the language of the web – so the same code works in both runtimes. -In node, this module is a simple torrent client, using TCP and UDP to talk to -normal torrent clients. Soon, it will gain the ability to swarm with web peers, making -it the first "hybrid" client. +In node.js, this module is a simple torrent client, using TCP and UDP to talk to +other torrent clients. In the browser, WebTorrent uses **WebRTC** (data channels) for peer-to-peer transport. It can be used **without** browser plugins, extensions, or installations. It's Just @@ -31,8 +30,10 @@ To make BitTorrent work over WebRTC (which is the only p2p transport that works web) we made some protocol changes. Therefore, a browser-based WebTorrent client can only connect to other clients that support WebTorrent (and WebRTC). -We hope established torrent clients (uTorrent, Transmission, Vuze, etc.) will add support -for WebTorrent (and WebRTC) so they can swarm with both normal *and* web peers. +The WebTorrent node.js module will soon gain the ability to connect to web peers using +WebRTC, making it the first "hybrid" client. We hope established torrent clients +(uTorrent, Transmission, Vuze, etc.) will also add support for WebTorrent (and WebRTC) so +they can connect to both normal *and* web peers. ![Network](img/network.png) |