Fix the description about APP_CONTROL_DATA_PATH

Change-Id: I933bcf0871906c947a33cdfb7bc3f9ea14a0b2fc
Signed-off-by: Hwankyu Jhun <h.jhun@samsung.com>

diff --git a/include/app_control.h b/include/app_control.h
index 42e0d92..48fd39f 100644 (file)
--- a/include/app_control.h
+++ b/include/app_control.h
@@ -390,7 +390,7 @@ typedef enum {
 /**
  * @brief Definition for app_control data: Paths of items
  * @since_tizen @if MOBILE 2.3 @elseif WEARABLE 2.3.1 @endif
- * @remarks Since Tizen @if MOBILE 2.4 @elseif WEARABLE 3.0 @endif, 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.
+ * @remarks Since Tizen @if MOBILE 2.4 @elseif WEARABLE 3.0 @endif, 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_PATH "http://tizen.org/appcontrol/data/path"