Opened 17 years ago

Last modified 17 years ago

#156 closed Bug report

Issues with new transfer system

Reported by: magra Owned by:
Priority: low Component: Other
Keywords: Cc: magra, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

The new separated transfer "thread" in Filezilla is nice
but the implementation has problems.

I think you must have a user definable file size, below
which the seperate connection is not established and
instead the "browsing" connection is used (as how it
worked before). When developing I tend to upload small
files repeatedly and before this was very quick, but now
every time I upload a file I have to wait about 15 seconds
everytime for the connection to be established.

Also, it appears that the second connection is dropped
as soon as the file/queue is transferred. I think you need
to add an option so that this connection is kept alive for
a specified duration of time. So when new transfers are
initiated it doesn't have to reconnect again (which on my
system takes around 10-15 seconds).

Change History (2)

comment:1 Changed 17 years ago by Tim Kosse

Thanks for your feedback.
In the next version all files below a certain size
(customizable, default 1024) will be transferred using the
primary connection.
Also, the transfer connection get's not disconnected
immediately, now there's a 30 seconds delay.

comment:2 Changed 17 years ago by Tim Kosse

both suggestions are implemented in 2.0.0

Note: See TracTickets for help on using tickets.