FarScp plugin open one connection for each command (every transfer, every directory listing), so it does not open shell and so it does not need to do all the sanity checks WinSCP does on startup. However WinSCP is subsequently much faster, because once it has opened connection it can do all command very quickly.
I 100% agree with you. WinSCP - quicker and has a lot of useful features! But FarSCP doesn't break connection after 'cd /incorrect_path/....' but WinSCP does. :-(
You may switch off some startup checks, if your server configuration allows it. See "Clear aliases", "Clear mational variables", "Alias LS to display group name", "Lookup user groups" on SCP tab of login dialog.
It's very good your plugin has such features but it's not clear (for me) what these options mean.
My server supports SSH v1 and SSH v2. It will be great if somebody explain what protocol version better to use with slow connection (32kbit/s) and what 'Encryption chipher' to use in this case...
Probably changing these option I can make WinSCP more faster. I think a lot of uses have similar questions
and it will be great if you supply WinSCP with help/docs/faq.
Also note that if your server supports SFTP, FarScp plugin uses SFTP, not SCP. So you probably compare uncomparable. You may try SFTP with WinSCP as well.
My server supports SCP only.
Actually I found the core of the problem:
'Remember last used directory' was checked and 'Remote directory' has incorrect path. So it was my side problem. Now WinSCP starts the session in 20-25 sec. i think it's normally for 32kbit/s channel.
Thanks for help.