You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Comparing rqbit side by side with transmission-gtk, I noticed that rqbit does not send Stopped event to a tracker when a torrent is paused from UI. When a torrent is paused from transmission-gtk UI, the Stopped event is sent. Started event is sent by both rqbit and transmission-gtk when a torrent is resumed from corresponding UIs.
I'm not sure if Stopped event needs to be sent in a case when a torrent is paused, just noting it here because transmission-gtk does send Stopped in this scenario, and it seems a tracker needs to remove the Stopped peer from its peer list that is mapped to info_hash it is tracking.
The text was updated successfully, but these errors were encountered:
Comparing rqbit side by side with transmission-gtk, I noticed that rqbit does not send Stopped event to a tracker when a torrent is paused from UI. When a torrent is paused from transmission-gtk UI, the Stopped event is sent. Started event is sent by both rqbit and transmission-gtk when a torrent is resumed from corresponding UIs.
I'm not sure if Stopped event needs to be sent in a case when a torrent is paused, just noting it here because transmission-gtk does send Stopped in this scenario, and it seems a tracker needs to remove the Stopped peer from its peer list that is mapped to info_hash it is tracking.
The text was updated successfully, but these errors were encountered: