The possible transfer modes for files specified in invocation requests.
Synopsis:
#include <bps/navigator_invoke.h>
typedef enum {
NAVIGATOR_INVOKE_FILE_TRANSFER_MODE_UNSPECIFIED = 0
NAVIGATOR_INVOKE_FILE_TRANSFER_MODE_PRESERVE = 1
NAVIGATOR_INVOKE_FILE_TRANSFER_MODE_COPY_RO = 2
NAVIGATOR_INVOKE_FILE_TRANSFER_MODE_COPY_RW = 3
NAVIGATOR_INVOKE_FILE_TRANSFER_MODE_LINK = 4
} navigator_invoke_file_transfer_mode_t;
Data:
- NAVIGATOR_INVOKE_FILE_TRANSFER_MODE_UNSPECIFIED
- Indicates that the file transfer mode has not been specified and the default logic should apply.
- NAVIGATOR_INVOKE_FILE_TRANSFER_MODE_PRESERVE
- Indicates that the file transfer handling should be skipped and the specified file URI should be passed to the target as-is.
- NAVIGATOR_INVOKE_FILE_TRANSFER_MODE_COPY_RO
- Indicates that the file should be transfered as a read only copy of the file specified in the URI attribute.
- NAVIGATOR_INVOKE_FILE_TRANSFER_MODE_COPY_RW
- Indicates that the file should be transfered as a read/write copy of the file specified in the URI attribute.
- NAVIGATOR_INVOKE_FILE_TRANSFER_MODE_LINK
- Indicates that the file should be transfered as a link to the file specified in the URI attribute.
Note that link mode requires that the original file support o+r. In addition, if the file has o+w then the sender must be the owner of the file.
Library:
libbps (For the qcc command, use the -l bps option to link against this library)
Description:
This enumeration defines the supported modes for handling file transfer when a file URI is provided that does not point to a file in the shared area. Unless NAVIGATOR_INVOKE_FILE_TRANSFER_MODE_LINK is specified, file transfer handling will transfer the file via the target's private inbox.