New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use channels for engine-torrent communication #62

Closed

vimpunk opened this issue Nov 22, 2020 · 1 comment

Labels

Owner

vimpunk commented Nov 22, 2020

Although currently there is no real 'engine' entity, we still want to communicate two things:

torrent sending a "DownloadComplete" event to engine
engine's ability to send a "Stop" command to torrent

These can be used to more cleanly implement stopping the torrent than how it is currently done.

Later of course this will expand to many more types of commands engine can send to torrent, and events torrent can send to engine.

vimpunk added the enhancement label

vimpunk mentioned this issue

Seed a torrent #50

Closed

13 tasks

Owner Author

vimpunk commented Dec 21, 2020

Closed by #73

vimpunk closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment