multithreaded-download-manager
multithreaded-download-manager copied to clipboard
Limit Download speed
Can you add a way to limit download speed per file?
I am not sure if this is possible with WebExtensions APIs. Maybe this API can be used to delay the data flow and control the speed. I need to do some experiments.
Unfortunately, this API does not show the expected behavior in my test. Suspending a download request does not stop the network transfer, but piles the data up instead. For example, I suspended the request for 3 seconds at the beginning of a local 10KB/s download task, and when the request was resumed, 30KB data came in instantly.
Now I think this feature requires new extension API in Firefox, and cannot be implemented currently. Please leave this issue open to track the status.
I was just about to request this integration, and then i saw this issue..
Regarding the need for a new API that would be able to limit the incoming data stream(s), i don't know if this has already been requested on the bugzilla forum. It must be said that this one is certainly the official, but from an ergonomic point of view it remains a bit crazy to explore, which is why i may have missed it.
I hope this feature will be implemented speedly.
I cannot found such feature request either. The API I mentioned above is part of StreamFilter APIs proposed by NoScript's developer, but I cannot find out whether it is intended to limit the network stream or not. From the test and the source, it seems that it cannot suspend the network in practice.
I cannot found such feature request either. The API I mentioned above is part of StreamFilter APIs proposed by NoScript's developer, but I cannot find out whether it is intended to limit the network stream or not. From the test and the source, it seems that it cannot suspend the network in practice.
When I accessed your link, i was surprised to see that it is Gecko's repository and not Quantum's.
Again idk how Firefox developers plan to fill the thermal gaps of WebExtensions APIs compared to the old XUL/XPCOM format...
@xerta555 The browser engine is still Gecko. New Quantum parts are developed and merged incrementally.
@xerta555 The browser engine is still Gecko. New Quantum parts are developed and merged incrementally.
I didn't know that, for me they annonced that Quantum completly replaced Gecko. I believe they had not mentioned that some parts of codes were still from Gecko.