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
It seems every UDP tracker present when a torrent is first added to a client consumes a socket for the lifetime of the client. This should be fixed so that sockets are only in use for the duration of an announce on a given tracker.
The text was updated successfully, but these errors were encountered:
I think this will require unexposing Connect() from the tracker interface. I may have been overly enthusiastic about exposing all concepts of a tracker from the first on this.
It seems every UDP tracker present when a torrent is first added to a client consumes a socket for the lifetime of the client. This should be fixed so that sockets are only in use for the duration of an announce on a given tracker.
The text was updated successfully, but these errors were encountered: