Dyalog Forums

Just another small point ..
It seems that many FTP users have similar problems with Binary FTP uploads .. even using standard FT-Client software.
So the "timeout" problem using Congo for Binary FTP-Uploads is probably not be a Conga problem.
ASCII uploads run without any problem .. on Conga or FTP-Clients.
FWIW

PS: Even with a disabled or no local Firewall including disabling my Router Firewall .. the Binary Upload is still not smooth.

It could of course be my own Router that is causing the problem :

Malicious routers, firewalls and data sabotage
http://wiki.filezilla-project.org/Network_Configuration#Malicious_routers.2C_firewalls_and_data_sabotage

Well, I decided to try using my old FTP code from 4 years ago again, just to see if it still worked. The old code uses the old Dyalog FTP Workspace .

I transferred 6 JPG files without a hitch .. each ca. 650 KB.

I repeated many times .. works perfectly.
( as well as Text files of course )

RUNFTPTEST
Testing Internet connection ...
220 Speak friend, and enter
331 FTP login okay, send password.
230 User logged in, proceed.
250 Directory changed to /
Connected to root
200 Using BINARY mode to transfer data.
200 PORT command successful.
150 Opening BINARY mode data connection.
226 Transfer complete. Closing data connection.
...
...
226 Transfer complete. Closing data connection.
200 Using BINARY mode to transfer data.
200 PORT command successful.
150 Opening BINARY mode data connection.
226 Transfer complete. Closing data connection.
226 Transfer complete. Closing data connection.
Ubertragung war OK !
221 Goodbye.

Does the new Conga code use different DLLs than the old FTP code I wonder ?

Anyway .. I'll now just carry on with the "old" FTP version ... unless someone comes up with an idea.

Thanks to all for the help.

kai wrote:originally "Client". In order to improve readability that was changed to "Clt"

Nice!

I mostly use FTP to get files rather than send them.

Switched an applications FTP from Conga to .NET a few months ago (after following up on Simon Marsden's post to the APL Wiki). Transfer times are dramatically better - whether this is a direct consequence or coincidence I don't know).

Might be worth checking out whether .NET for FTP might solve any problems.

kai wrote:In Conga (DRC that is) the name was originally "Client". In order to improve readability that was changed to "Clt in Conga 2.0.

Interesting theory :-). In fact, Conga 2.0 has a new function Clt which combines the old Client and SecureClient functions into a single function. The same change was made for Srv (Server + SecureServer). The changes are discussed in the Conga 2.0 Users Guide, which you can find at http://www.dyalog.com/documentation/12.1/index.htm. We decided that the number of users of Conga was still quite small at the time, so we allowed ourselves this change to the interface. I don't think we'll be able to do that again, it may have been a mistake already.

You will need to use the DRC namespace which matches (was shipped with) your Conga DLL.

I see that the FTPClient class has one reference to the old function, in the PutData method. Unfortunately our QA scipt does not do a PutData, or we would have found it :-(.

Simply replace the function name in the line in question:

[7] :If 0=⊃(r conn)←DRC.Clt''Host DataPort type(10+⍴Data)

Hi Morten,
I already did that , but the actual problem was that on uploading larger files, the FTP hung on a Timeout. I am now using the old FTP workspace - with out any problems.

I thought at first it was because my test-file was Binary, but on more experimenting , I discovered that it I had the same Timeout problem when uploading a large ASCII files.





It would be nice if someone else tried to upload a large file using Conga from their PC.

The only thing I can think of is that maybe my WinXP SP2 drivers are not up-to-date !
.. or this a Conga coding problem ?
Cheers
phil

It would be nice if someone else tried to upload a large file using Conga from their PC.

Has anyone tried this yet ?
TIA

Hi Phil,

I've contacted Bjørn. He has tried larger file transfer via Conga and FTP. It works, but you first have to increase the timeout in the FTPCLient as the standard setting will timeout as larger files take longer to transfer.

Regards,

Vince

Hi Vince,
as I said, I'd already tried varying the timeouts, but thanks anyway.

My conclusion after doing some more expirimenting : My firewall is the problem.

I used Conga to upload varying sizes in steps of 500K, to discover that at ca. 3.5 MB, the problems start. I disabled the firewall, and retried the Conga code as well as the "Filezilla FTPClient" both to no avail - my guess is that the firewall may not be "completely" disabled ( Outpost ).
I retried the Filzilla transfers on another PC that had no firewall installed - the 3.5 MB file transferred successfully after second attempt ( the first one timed out ).

So I'll now close this discussion - seems I was on the wrong path in thinking Conga might be the problem.
Thanks everyone !

Does anybody know if Conga can function as an SFTP client?

If not, any other suggestions on what to use (from within APL)?

thanks.