* with this file, You can obtain one at http://mozilla.org/MPL/2.0/.
******************************************************************************/
/**
- * \file persistence_client_library_key.h
+ * \file persistence_client_library.h
* \ingroup Persistence client library
* \author Ingo Huerner (XSe) / Guy Sagnes (Continental)
* \brief Header of the persistence client library.
* \par change history
* Date Author Version
* 25/06/13 Ingo Hürner 1.0.0 - Rework of Init functions
+ * 04/11/13 Ingo Hürner 1.3.0 - Added define for shutdown type none
*
*/
/** \ingroup GEN_PERS */
-/** \defgroup PERS_CLIENT Client: initialisation access
+/** \defgroup PERS_CLIENT Client: initialization access
* \{
*/
/** \defgroup PERS_CLIENT_INTERFACE API document
* \{
*/
+/**
+ * @mainpage The Persistence Client Library documentation
+ * GENIVI's Persistence Client Library, known as PCL, is responsible for handling persistent data,
+ * including all data read and modified during a lifetime of an infotainment system.<br>
+ * "Persistent data" is data stored in a non-volatile storage such as a hard disk drive or FLASH memory.
+ * <br><br>
+ * The Persistence Client Library (PCL) provides an API to applications to read and write persistent data
+ * via a key-value and a file interface.<br>
+ * It also provide a plugin API to allow users to extend the client library with custom storage solutions.
+ *
+ * @section doc Further documentation
+ * @subsection docUser User Manual
+ * There is a a user manual for the client library available,
+ * see: http://docs.projects.genivi.org/persistence-client-library/1.0/GENIVI_Persistence_Client_Library_UserManual.pdf
+ *
+ * @subsection docArch Architecture Manual
+ * For more information about the persistence architecture,
+ * see: http://docs.projects.genivi.org/persistence-client-library/1.0/GENIVI_Persistence_ArchitectureDocumentation.pdf
+ *
+ *
+ * @section plugin Custom plugin configuration file
+ * @attention
+ * The plugin configuration file has been changed!
+ *
+ * The configuration file has now the following format<br>
+ * <predefinedPluginName> <pathAndLibraryName> <loadingType> <initType>
+ *
+ * <b>Predefined plugin name</b><br>
+ * Use one of the following names:
+ * - early => predefined custom library for early persistence
+ * - secure => predefined custom library for secure persistence
+ * - emergency => predefined custom library for emengency persistence
+ * - hwinfo => predefined custom library for hw information
+ * - custom1 => custom library 1
+ * - custom2 => custom library 2
+ * - custom3 => custom library 3
+ *
+ * <b>Path and library name:</b><br>
+ * The name and path of the library
+ *
+ * <b>Valid loading type:</b>
+ * - "init" ==> if the plugin must be laoding during the pclInitLibrary function
+ * - "on" ==> if on demand laoding of the plugin is requested. The plugin will be loaded
+ * when a plugin function will be loaded the first time
+ *
+ * <b>Init Type:</b>
+ * - sync ==> use the "plugin_init" function for plugin initialization
+ * - async ==> use the "plugin_init_async" function for plugin initialization
+ *
+ * <b>Example:</b><br>
+ * hwinfo /usr/local/lib/libhwinfoperscustom.so init async
+ *
+ * @note
+ * Make sure that there is only ONE blank between each entry and no blank at the end of the file.
+ * The parser has been optimized for speed, so there is less error checking.
+ */
+
+
+
#ifdef __cplusplus
extern "C" {
#endif
* \{
*/
-#define PERSIST_API_INTERFACE_VERSION (0x01000000U)
+#define PERSIST_API_INTERFACE_VERSION (0x01030000U)
/** \} */
-/** \defgroup PCL_OVERALL functions for Library Initialisation
- * The following functions have to be called to allow intialisation of the internal interfaces.
+/** \defgroup SHUTDOWN_TYPE notifications type definitions
+ * according to Node State Manager Component
* \{
*/
+#define PCL_SHUTDOWN_TYPE_FAST 2 /// Client registered for fast lifecycle shutdown
+#define PCL_SHUTDOWN_TYPE_NORMAL 1 /// Client registered for normal lifecycle shutdown
+#define PCL_SHUTDOWN_TYPE_NONE 0 /// Client does not register to lifecycle shutdown
+/** \} */
+
+
+/** \defgroup PCL_OVERALL functions for Library initialization
+ * The following functions have to be called for library initialization
+ * \{
+ */
+
+
+#define PCL_SHUTDOWN 1 /// trigger shutdown
+#define PCL_SHUTDOWN_CANEL 0 /// cancel shutdown
+
+
/**
- * @brief initalize client library
+ * @brief initialize client library.
+ * This function will be called by the process using the PCL during startup phase.
*
* @attention This function is currently N O T part of the GENIVI compliance specification
*
* @param shutdownMode shutdown mode ::PCL_SHUTDOWN_TYPE_FAST or ::PCL_SHUTDOWN_TYPE_NORMAL
*
* @return positive value: success;
- * On error a negative value will be returned with th follwoing error codes:
- * ::EPERS_LOCKFS, ::EPERS_NOT_INITIALIZED
+ * On error a negative value will be returned with the following error codes:
+ * ::EPERS_NOT_INITIALIZED, ::EPERS_DBUS_MAINLOOP,
+ * ::EPERS_REGISTER_LIFECYCLE, ::EPERS_REGISTER_ADMIN
*/
int pclInitLibrary(const char* appname, int shutdownMode);
/**
* @brief deinitialize client library
+ * This function will be called during the shutdown phase of the process which uses the PCL.
*
* @attention This function is currently N O T part of the GENIVI compliance specification
*
* @return positive value: success;
- * On error a negative value will be returned with th follwoing error codes: ::EPERS_LOCKFS
+ * On error a negative value will be returned.
*/
int pclDeinitLibrary(void);
+
+
+
+/**
+ * @brief pclLifecycleSet client library
+ * This function can be called if to flush and write back the data form cache to memory device.
+ * The function is only available if PCL_SHUTDOWN_TYPE_NONE has been used in pclInitLibrary.
+ *
+ * @attention This function is currently N O T part of the GENIVI compliance specification
+ * @attention In order to prevent misuse of this function the cancel shutdown request
+ * can only be called 3 times per lifecycle.
+ * If this function has been called by an application more then 3 times the application
+ * will not be able to store it's data anymore during the current lifecycle.
+ * The application isn't fully operable in this lifecycle anymore.
+ * In the next lifecycle the application can store data again until the limit above
+ * has been reached.
+ *
+ * @param shutdown PCL_SHUTDOWN for write back data when shutdown is requested,
+ * and PCL_SHUTDOWN_CANEL when shutdown cancel request has been received.
+ *
+ * @return positive value: success;
+ * On error a negative value will be returned with the following error codes:
+ * ::EPERS_COMMON, ::EPERS_SHUTDOWN_MAX_CANCEL, ::EPERS_SHUTDOWN_NO_PERMIT
+ */
+int pclLifecycleSet(int shutdown);
+
+
/** \} */
+#ifdef __cplusplus
+}
+#endif
+
/** \} */ /* End of API */
/** \} */ /* End of MODULE */
+
#endif /* PERSISTENCY_CLIENT_LIBRARY_H */