If you’re trying to migrate an FTP server to the cloud, you may be dealing with gotchas related to UNIX vs Windows text file formats.
Here at Files.com, we are built entirely on Linux (and in fact, the company that makes the version of Linux we use, Canonical, is a happy customer of ours too!).
But we also have deep experience with Windows and we love all our Windows-based resellers and customers, so we’ve put considerable time and effort into ensuring compatibility with Windows-based apps and workflows.
In fact, we are (as far as we know) the only service to offer a Windows compatibility mode for FTP, giving you the ability to emulate older versions of Windows-based FTP servers.
When might I need to use Windows FTP server mode?
While a standard UNIX-style FTP server is perfectly sufficient in most cases, some less common FTP clients (such as those in POS devices or other embedded systems) are quite limited in their configurability. For example, an FTP client may be “hard-coded” for communicating with Windows FTP servers in text/ASCII transfer mode. Since this transfer mode alters files by automatically converting line-endings from Windows format (CR+LF) to UNIX format (LF), any processes that depend on file contents remaining unchanged after transfer could break.
The Windows FTP mode feature in Files.com fully addresses this problem by treating both ASCII and binary mode file transfers the same. This ensures that transferred files remain unaltered, regardless of the transfer mode that the client is using.