FTPCreateDisposition Enumeration |
Denotes how file creation is managed in FTP transfers
Namespace:
NetQuarry
Assembly:
EAP.Core (in EAP.Core.dll) Version: 2.0.0.0 (4.6.8.0)
Syntax [FlagsAttribute]
public enum FTPCreateDisposition
<FlagsAttribute>
Public Enumeration FTPCreateDisposition
Members
| Member name | Value | Description |
---|
| createNew | 1 | A new file is created; if the file already exists the method fails. |
| createTruncate | 2 | A new file is created; if the file already exists, it is opened and truncated. |
| openExisting | 4 | An existing file is opened. If the file does not exist the method fails. |
| openOrCreate | 8 | If the file exists, it is opened. If the file does not exist, it is created. |
| truncateExisting | 16 | An existing file is opened and truncated. If the file does not exist the method fails. |
| appendData | 32 | Data is always written at the end of the file. Data is not required to be appended atomically. This means that if multiple writers attempt to append data simultaneously, data from the first may be lost. |
| appendDataAtomic | 64 | Data is always written at the end of the file. Data MUST be written atomically so that there is no chance that multiple appenders can collide and result in data being lost. |
| textMode | 128 | Indicates that the server should treat the file as text and convert it to the canonical newline convention in use. When a file is opened with this flag, data is always appended to the end of the file. Servers MUST process multiple, parallel reads and writes correctly in this mode. |
| blockRead | 256 | The server MUST guarantee that no other handle has been opened with read access, and that no other handle will be opened with read access until the client closes the handle. (This MUST apply both to other clients and to other processes on the server.) In a nutshell, this opens the file in non-sharing mode. |
| blockWrite | 512 | The server MUST guarantee that no other handle has been opened with write access, and that no other handle will be opened with write access until the client closes the handle. (This MUST apply both to other clients and to other processes on the server.) In a nutshell, this opens the file in non-sharing mode. |
| blockDelete | 1024 | The server MUST guarantee that the file itself is not deleted in any other way until the client closes the handle. No other client or process is allowed to open the file with delete access. |
| blockAdvisory | 2048 | |
| noFollow | 4096 | If the final component of the path is a symlink, then the open MUST fail. |
| deleteOnClose | 8192 | The file should be deleted when the last handle to it is closed. (The last handle may not be an sftp-handle.) This MAY be emulated by a server if the OS doesn't support it by deleting the file when this handle is closed. |
| accessAuditAlarmInfo | 16384 | The client wishes the server to enable any privileges or extra capabilities that the user may have in to allow the reading and writing of AUDIT or ALARM access control entries. |
| accessBackup | 32768 | The client wishes the server to enable any privileges or extra capabilities that the user may have in order to bypass normal access checks for the purpose of backing up or restoring files. |
| backupStream | 65536 | This flag indicates that the client wishes to read or write a backup stream. A backup stream is a system dependent structured data stream that encodes all the information that must be preserved in order to restore the file from backup medium. The only well defined use for backup stream data read in this fashion is to write it to the same server to a file also opened using the backupStream flag. However, if the server has a well defined backup stream format, there may be other uses for this data outside the scope of this protocol. |
See Also