Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign uptorrent.on events of client.seed and client.add #749
Closed
Comments
This comment has been minimized.
This comment has been minimized.
|
It seems like this is not just affecting the ones from I edited the title |
This comment has been minimized.
This comment has been minimized.
|
Can only be accessed sync. Added the note here #750 and also added uploaded event. |
This comment has been minimized.
This comment has been minimized.
|
@Tercus This is what your example should look like: var torrent = client.seed(torrentfile, { announceList: [['ws://localhost:8080']] }, onseed)
torrent.on('infoHash', function() { console.log('infoHash') })
torrent.on('metadata', function() { console.log('metadata') })
torrent.on('ready', function() {
console.log('ready')
torrent.on('done', function() { console.log('done') })
torrent.on('download', function() { console.log('download') })
torrent.on('wire', function() { console.log('wire') })
})
function onseed (torrent) {
console.log('onseed getting called')
} |
This comment has been minimized.
This comment has been minimized.
|
This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have the following testcode:
Of all the torrent.on events, only the event "done" gets called and only on the client.on part of the code.
A dedicated torrent.on('seeding') and/or other events would be great to figure out when a torrent is actually starting/ready to seed.