Differences

This shows you the differences between two versions of the page.

--- cloudappliance/sftpsetup [2019_11_12 15:48] – dan
+++ cloudappliance/sftpsetup [2020_01_14 15:42] – dan
@@ Line 1: / Line 1: @@
 # FTP/SFTP Configuration
-##### last updated: Nov. 12, 2019
+##### last updated: Jan. 14, 2020
 The File Fabric Appliance and SaaS support a number of protocol gateways allowing applications to natively access the File Fabric using FTP/FTPS, SFTP or WebDAV. These are ideal for retrofitting existing applications for object storage.
@@ Line 14: / Line 14: @@
  * [[cloudftp]]
  * [[cloudappliance/appliance-troubleshooting|]]
+<WRAP center round info 100%>
+CloudFTP and the File Fabric's other protocol gateways allow your client program to work with the File Fabric using the enabled protocol. Communication between the File Fabric and the underlying storage, however, still occurs using the storage protocol as implemented by the specific connector used to connect the File Fabric to the storage.
+For example, you may upload a file to SwiftStack through the File Fabric storage using the File Fabric's CloudFTP gateway, but the File Fabric will upload the file to the SwiftStack storage using the Swift protocol.  This means that the settings you chose when you attached the SwiftStack storage to the File Fabric will be used.
+Continuing with our example, if the file you are uploading is larger than the storage's single object size limit (often 5GB) then you will need to have either static large objects or dynamic large objects enabled in the provider settings.  Otherwise the upload will fail.
+</WRAP>
 ## Initial Setup