Seeking the archive of ML and the reference manual, I found an option to
choke data transmission with MAXIMA=bps:128k or so. It seems applicable
only to HTTP and FTP. And since it can be used as a MOUNT option, maybe
choking regarding the destination server or source client, possibly based
on proxy authentication, is possible.
But unfortunately, it seems not applicable to SOCKS, or HTTPS (over
2014-12-26 11:32 GMT+09:00 Sergey Cher <firstname.lastname@example.org>:
> Hello Yutaka,
> i would love too see SOCK and http/https proto with limits and etc
> per user - by authentication, you are right.
> speed limit, yes, bandwidth limit/bandwidth total or Mbits - all this is
> limits are needed for users, some times 1 user use more server, then 2nd
> dosnt have nedded resourses at all
> 2000-00-00 0:0X GMT+02:00 佐藤豊 <email@example.com>:
>> Hi Serg,
>> Tell me more about your case to make the requirement clear.
>> - The application protocol you use
>> - What does the "per user" means; Is "user" identified by authentication?
>> - What does the "speed" means, as MBytes per minute or so
>> Cheers from Japan,
>> 2014-12-25 22:04 GMT+09:00 Sergey Cher <firstname.lastname@example.org>:
>>> Hello Yutaka,
>>> can you please make per user speed limit in Delegate sofrware ?
>>> Thank you for you great soft.
>>> A Delegate fan.