This is just a general idea and might not be well suited for fileshare. If that's the case, just say so and close this request.
I just thought I'd mention it, in case someone finds it useful.

Since fileshare is there to transmit files there might be of some use to have a throttling feature present, perhaps to only allow one simultaneous per user or perhaps by only allowing 4 (or any number) in total at any one time.
As throttling is implemented now in drupal, the fileshare could be inactivated by a high number of users on the site, but not by how many simultaneous downloads there are.

As I said. It's just an idea and if it's too hard to do or of no interest, feel free to just disregard it.

Comments

dboune’s picture

Thanks for the tickle.

To add...

Does throttling belong in PHP/Drupal, or elsewhere?
As is the usual point with Drupal, not everyone has the same access to the system configuration and network supporting a particular Drupal site. A Fileshare could very well soak up the possibly already externally throttled resource in an undesirable manner, and there is not some other mechanism of per-connection throttling available. This part of the question has really already been answered before.

Does throttling belong in Fileshare?
There is a subject related module in drupal core called Throttle. Should the type of throttling needed by Fileshare be controlled through or using that mechanism? Would any changes to Throttle be needed to support this, and would Throttle want those changes?
Reference: http://drupal.org/handbook/modules/throttle

How should throttling options be provided to the user?
Optionally on a per-fileshare basis in the node edit form makes the most sense to me, with an optional whole-pool restriction available in Administration. Restriction by the number of files being downloaded would be the easiest way to provide basic control. The concept of ul/dl ratios or other forms of control could be added later if ever wanted. Flow rate control could very well be on the higher end of difficulty, or not reasonable.

~Damian

haeger’s picture

Status: Active » Closed (won't fix)

I'm closing this bug now. No sense in keeping it open as it won't be fixed.