FileTransferMode

Since: BlackBerry 10.0.0

#include <bb/system/FileTransferMode>

To link against this class, add the following line to your .pro file: LIBS += -lbbsystem

The types of transfer that can be applied to a file during invocation.

When an invocation is sent containing a URI with a scheme of "file://" and with a path that references a file that is not in the shared area, a file transfer mode may be applied to transfer the file to the target's private inbox. This enumeration allows the sender to control how and if the private transfer is performed. Using this enumeration the sender can skip the private transfer, transfer by copy as a readable file, as a readable and writable file, or as a hard link to the original file.


Overview

Public Types Index

enum Type

Unspecified = 0, Preserve = 1, CopyReadOnly = 2, CopyReadWrite = 3, Link = 4

Public Types

Type

The types of transfer that can be applied to a file during invocation.

Since:

BlackBerry 10.0.0

Unspecified = 0

Use the default behavior specified by the invoke service.

Since:

BlackBerry 10.0.0

Preserve = 1

Skip file transfer handling and deliver the file as-is.

Since:

BlackBerry 10.0.0

CopyReadOnly = 2

Create a read only copy of the file in the target's private inbox.

Since:

BlackBerry 10.0.0

CopyReadWrite = 3

Create a read/write copy of the file in the target's private inbox.

Since:

BlackBerry 10.0.0

Create a hard link to the file in the target's private inbox.

When a hard link is specified, the permissions on the file must allow other users to read it (i.e., in UNIX-style file permissions, o+r). In addition, if the file permissions allow other users to both read and write (i.e., in UNIX-style file permissions, o+rw), then the sender must have write access to the file.

Since:

BlackBerry 10.0.0

Last modified: 2014-03-13

comments powered by Disqus