search

mafintosh / torrent-stream

The low level streaming torrent engine that peerflix uses
MIT License
1.94k stars 228 forks source link

Problem with connection to wires #92

Closed Kureev closed 9 years ago

Kureev commented 9 years ago

Hi @mafintosh , I'm wondering if you can explain (or show me where to find it) the difference between torrent-stream and uTorrent (for example) connection mechanism. Sometime torrent-stream (and peerflix) unable to start streaming. As i understood, the problem is that all of the wires are choked. Can you tell me why it happens and does it possible to avoid it somehow?

mafintosh commented 9 years ago

When it doesn't start are you still connected to any wires? (what does swarm.wires.length return?)

Kureev commented 9 years ago

Yes, it returns > 0, but all of them are chocked. The point is that if i try to do the same thru uTorrent (for example), it works fine.

By the way, is it possible to download a "private" torrents? For example at soap4.me i can download the torrent file, but when i'm trying to stream it, i'm not able to download even a bit. (With native clients like Transmission or uTorrent works fine)

wiebemarten commented 9 years ago

"private" torrents mean that only select people can use/know of a certain tracker. I think that as soon as you provide a tracker to the custom tracker list of the torrent-stream options, it should be able to download it.

jaruba commented 9 years ago

I'm having a similar issue, I use peerflix (obviously with torrent-stream) in node-webkit, and if the engine is dorment for a while, it disconnects all peers and does not download anymore if I .select() a file or try to access a http stream.

.swarm.wires.length returns 0, how can I restart a peer check?

I tried .swarm.pause() then .swarm.resume(), but it didn't change anything..