Skip to main content
Solved

FTPCaller VS SystemCaller for FTP Calls

  • May 30, 2018
  • 1 reply
  • 37 views

Hello All,

I am posting this question to try to gain an in-depth understanding of the functionality of FTPCaller vs SystemCaller.

I designed a script that used SystemCaller to call on CoreFTP in order to upload and overwrite a file to a certain site and log the results in a text document.

This is the SystemCaller command:

""C:\\Program Files\\CoreFTP\\Coreftp.exe" -O -u @Value(file_path) @Value(site_command) -log "@Value(routinglogdirectory)@Value(_rootname).log"

The command worked successfully. It took 12 seconds to run.

I switched to an FTPCaller to run the same function.

The time was reduced to 1 second.

Just for my understanding, I am wondering what is FTPCaller doing differently in the background? Would love to hear some insights from FME.

Thanks,

Fariya

Best answer by jdh

Well for starters, there's no overhead in opening coreFTP.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

jdh
Contributor
Forum|alt.badge.img+38
  • Contributor
  • Best Answer
  • May 30, 2018

Well for starters, there's no overhead in opening coreFTP.