-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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.
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
upload/download events fire for tracker traffic #2486
Comments
without recalculating the data transfered, afaik no, I've known about this for ages now and decided to intentionally keep it this way because it then becomes harder for webtorrent to become leechware, as setting upload to 0 will also stop all download as you cant query trackers |
I'm not asking to turn off upload, i just want to segregate the traffic metrics |
For speed limit, I don't care. |
like.. even a boolean on an upload/download event to tell me if the xfer was chunk data or metadata would really help me out |
yes but decoupling the 2 means speed limit would no longer throttle tracker traffic |
Does an upload event ever fire for both tracker traffic AND chunk data at once? |
for the 3rd time, yes! |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
Can you enable a way to distinguish between other protocol traffic vs torrent chunk data transfer?
The text was updated successfully, but these errors were encountered: