I am writing integration with a third party SaaS based content delivery platform. I have no access to the platform's servers with the exception of using the existing web services API and FTP functionality offered by the platform.
The obvious way to store Tridion published data in a custom way is to write a custom storage/deployer extension, but for the reasons stated above, the deployer cannot be installed on the destination servers. As such we are considering publishing to the local file system, and installing the custom deployer on the CM server, and having it distribute the necessary to the delivery servers via FTP and Web Service calls.
What are the pros and cons of such an approach, and would there a better extension point such as the transport service? Any ideas/suggestions would be welcomed.