Quick connection doesn't resue command socket thread

[crouch]

Although I limit the socket thread num to 1, by set Menu->Edit->Settings->transfers->max simutaneously transfers to 1, the quick connections cannot reuse the command socket thread. Only if I connect to the site from the site manager, it works.
And a similiar thing is the locale. Although the ftp specification requires the server to use utf-8 locale, but old ftp site and ftp server softwares may still use the multi-byte locale. So I think a locale setting for quick connections is necessary.

[Tim Kosse]

What is a "command socket thread"?

I won't add any of the advanced site settings to the Quickconnect bar, as it would make it too complex for a Quickconnect bar.

[crouch]

I didn't mean real thread. "command socket thread" means the connected socket to which the ftp client sent PWD, CWD, LIST and so on. While the data transfer like RETR should be sent in the SAME socket of PWD, if the site limits the maximum socket link per client to 1. But filezilla3's behaviour is not like this, if the size is connected from quick connecting bar. It just try to open one more socket to RETR the file.

The setting of locale of quick connection is not necessarily put on the bar, and just some place in Menu->Setting will be OK.

[Tim Kosse]

This is by design so that you can still browse the server while transferring a file.

[crouch]

Yes, browsing while transferring is a feature, but it should be allowed only if the sever set the maximum socket link per client to 2 or larger.