From ba3d2dfcffab1ff4397b236b8ec121f88d394bfa Mon Sep 17 00:00:00 2001 From: Junghoon Park Date: Wed, 27 Jul 2016 12:57:39 +0900 Subject: [PATCH] Add description for APP_CONTROL_DATA_SELECTED Change-Id: If0a924204a329c9917d437a6b48a6536bb208d6b Signed-off-by: Junghoon Park --- include/app_control.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/app_control.h b/include/app_control.h index 48fd39f..0ce6743 100644 --- a/include/app_control.h +++ b/include/app_control.h @@ -383,6 +383,7 @@ typedef enum { /** * @brief Definition for app_control data: Selected items * @since_tizen @if MOBILE 2.3 @elseif WEARABLE 2.3.1 @endif + * @remarks Since Tizen 3.0, if all added paths with this key are under the caller application's data path which can be obtained by calling app_get_data_path() function, those will be shared to the callee application. Framework will grant a temporary permission to the callee application for those files and revoke it when the callee application is terminated. Paths should be regular files. The callee application can just read them. Note that the callee application doesn't have read permission of the directory that is obtained by caller's app_get_data_path(), you should open the file path with read only mode directly. For example, access() call to the file path will return error because access() needs the read permission of the directory. The callee application can call open() with O_RDONLY mode for the passed file path, because framework grants read permission to the passed file path. */ #define APP_CONTROL_DATA_SELECTED "http://tizen.org/appcontrol/data/selected" -- 2.7.4