Skip to content
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

Closed
ftreesmilo opened this issue Feb 19, 2023 · 8 comments
Closed

upload/download events fire for tracker traffic #2486

ftreesmilo opened this issue Feb 19, 2023 · 8 comments
Labels

Comments

@ftreesmilo
Copy link
Contributor

Can you enable a way to distinguish between other protocol traffic vs torrent chunk data transfer?

@ThaUnknown
Copy link
Member

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

@ftreesmilo
Copy link
Contributor Author

I'm not asking to turn off upload, i just want to segregate the traffic metrics

@ftreesmilo
Copy link
Contributor Author

For speed limit, I don't care.

@ftreesmilo
Copy link
Contributor Author

ftreesmilo commented Feb 19, 2023

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

@ThaUnknown
Copy link
Member

yes but decoupling the 2 means speed limit would no longer throttle tracker traffic

@ftreesmilo
Copy link
Contributor Author

Does an upload event ever fire for both tracker traffic AND chunk data at once?
Again, I don't care if you keep speed limit the way it is, I just want the data identified in the metrics.

@ThaUnknown
Copy link
Member

ThaUnknown commented Feb 19, 2023

@github-actions
Copy link

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

@github-actions github-actions bot added the stale label Apr 21, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 29, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants