Output to an ftp server via Destinations or Applescript

Question

In Compressor, you can set the Destination of a compression batch to be a remote server, such as an ftp server.
When you start a batch, if the destination is not available or reachable then the documentation (p.230) says: "When there is a problem with your destination, a yellow warning triangle appears. You must resolve this problem before you can successfully transcode."
Although I have not tried it, it implies that if your remote ftp server is not accessible when you drop a file on a created droplet with the Destination set to an ftp server, it won't be able to begin encoding until the destination is available: "As soon as you resolve the problem, the warning triangle disappears and you can continue to transcode." (p.230)
For a lot of people, this is OK.
Some people need to compress and then tranfer the output to a distant location, and they may not have continuous, reliable access to the remote location. They may need to make a temporary connection via modem dial-up, satellite phone or third-world Internet connections. Think news reporters in remote locations.
So, for those people, the option of Applescript should allow them to have their output files saved to a local destination, and then staged up to the ftp server using the built-in commands. But, the problem is that a small file is created at the Destination when the compression is started, and Compressor is not Applescript aware (apart from being able to call an Applescript). This means that any Applescript called as a post processing activity knows nothing about the files Compressor just processed and outputted. It has to glean information about them from the Destination folder where the output files are placed, and then sort out the completed output files from the ones that have just been started, then ftp the completed files up to an ftp server and delete sent files from the Destination folder.
What I would like to see is either
1) a Staged Destination where files are created on the first Destination then staged to a secondary Destination, with an option of keeping these files on the first destination, and/or
2) Applescript support in Compressor which will allow information about the files that have just been compressed to be passed to another Applescript aware application or script.
I would be happy even with some sample Applescript to do the transfer or files from Destination to an ftp server that avoids copying files that haven't been fully processed.
Has anyone else run into these issues?
Bill Lee

Answer 1

Oh, trust me, I do know about Apple and the fact this discussion site is not an official contact point for Apple. I'll be escalating this Request for Enhancement through my contacts at Apple.
There is a reason I have not posted before in this forum (and relates to the above).
There seems to be few people who are using the Applescript post-processing feature, and I was trying to gauge any support for enhancements in this area (and maybe stir up some villagers with pitchforks and burning torches).
Apple will listen to normal users input, but it needs to have a business case that justifies any resources devoted to this. The more people affected, and the greater the impact on your business, and the size/importance of your business has an effect on whether you will get what you want, and when.
Sorry if I was not clear on what I wanted: information as whether this was important for other (non-Apple) people, and whether people had scripts that solved the problem of staging output files to an ftp server that was not consistently connected during the compression process.
Thanks for your reply,
Bill Lee