Custom Query (7985 matches)
Results (214 - 216 of 7985)
I am using 126.96.36.199 nightly build. After a minut or so i am getting a "421 Timeout" message, which logs my off. The setting 0 - 9999 doesn't seem to work.
|#7990||duplicate||timed bandwidth throttle mechanism (speed limit)|
With limited bandwidth being shared Filezilla can be a bit of a data hog.
Can I suggest a kb/sec download limit maximum transfer rate. This is a similar mechanism that some bit torrent clients have (Vuze)
I would also imagine an improvement over this feature that would allow a timetable of transfer rates. This would for example allow an increase in transfer rates after office hours, or overnight when the network is idle.
An example would be below:
Start End Download Bandwidth Upload Bandwidth 0830 - 1730 10k bytes per sec 5k bytes per sec 1731 - 2000 50k bytes per sec 20k bytes per sec 2001 - 0700 unlimited unlimited 0701 - 0829 50k bytes per sec 20k bytes per sec
I think this would a very good feature in shared network environments and for unattended operation of backups/large complex transfers.
I would suggest having separate upload and download limits for people with asymmetrical bandwidth connectivity.
|#5071||outdated||time/datestamp showing 00 for seconds on all files|
The seconds portion of time/datestamp always displays "00" on all files on our AIX servers. I am using filezilla client version 3.3.01. The date and hour:min are all correct only the seconds are affected. I just noticed this but am sure that this was not the case in the past.