On 6 Oct 2015, at 2:44pm, David Barrett <dbarrett at expensify.com> wrote:
> Regardless, all those solutions require me to wait for the entire backup to > complete before sending the file to the remote host -- my goal is to send > it one page at a time (eg, send the pages as the backup API processes them) > so as to avoid the large delay and disk space of the backup itself. In that case it's probably best, as was suggested by Clemens, to use a network filing system to allow a computer to access both the source file storage and the destination file storage. By opening a file on the remote filespace using SQLite you can use the Backup API to write directly to the destination filespace. Simon.
