WebTorrent now works in the browser, end-to-end

Re:WebTorrent now works in the browser, end-to-end by JulianMorrison on Monday September 15, 2014 @05:35AM (#8317963)

Client-server is faster if the server's upload speed can match the client's download speed, for all clients. Which implies a large, central server.

[ Parent | on HN ]

Re:WebTorrent now works in the browser, end-to-end by jacquesm on Monday September 15, 2014 @05:40AM (#8317976)

There are other parameters that are useful when evaluating a configuration besides just speed. Resilience is one of those, as is long term availability. Torrents seem to do quite well in the resilience department, I'm not sure how well they do when it comes to long term availability. Maybe someone has already studied that, it would seem to be the torrent equivalent of 'link rot', and quite possibly it is very high.

[ Parent | on HN ]

Re:WebTorrent now works in the browser, end-to-end by sktrdie on Monday September 15, 2014 @05:42AM (#8317980)

Sorry, what I meant by speed is: the ability to quickly access small sized resources such as HTML pages. The initial handshake required for P2P systems makes this process slower. Obviously for larger files where there are lots of peers serving the content, you can get better speeds.

[ Parent | on HN ]

Re:WebTorrent now works in the browser, end-to-end by tlrobinson on Monday September 15, 2014 @07:34AM (#8318232)

Latency is also a factor.

[ Parent | on HN ]