ParameterMgr: add a method to forcefully disable the remote interface

In some setup, users might not want to start the remote interface even if the
toplevel configuration file allows it.

The parameter-framework client can now override the remote interface starting
policy. This was, until now, only dictated by the 'TuningAllowed' attribute in
the toplevel configuration file and the presence of the libremote-processor
library.

This method is forwarded to the connectors and the bindings.

Change-Id: Ib6dc272dfc7114125fdafd1a58642cde88847752
Signed-off-by: David Wagner <david.wagner@intel.com>

1 files changed, 17 insertions, 0 deletions

diff --git a/parameter/ParameterMgr.h b/parameter/ParameterMgr.h
index de948ba..c6a2fd5 100644
--- a/parameter/ParameterMgr.h
+++ b/parameter/ParameterMgr.h
@@ -143,6 +143,17 @@ public:
     // Dynamic parameter handling
     CParameterHandle* createParameterHandle(const std::string& strPath, std::string& strError);
 
+    /** Is the remote interface forcefully disabled ?
+     */
+    bool getForceNoRemoteInterface() const;
+
+    /**
+     * Forcefully disable the remote interface or cancel this policy
+     *
+     * @param[in] bForceNoRemoteInterface disable the remote interface if true.
+     */
+    void setForceNoRemoteInterface(bool bForceNoRemoteInterface);
+
     /** Should start fail in case of missing subsystems.
       *
       * @param[in] bFail: If set to true,  parameterMgr start will fail on missing subsystems.
@@ -614,6 +625,12 @@ private:
     ILogger* _pLogger;
     mutable uint32_t _uiLogDepth;
 
+    /** If set to false, the remote interface won't be started no matter what.
+     * If set to true - the default - it has no impact on the policy for
+     * starting the remote interface.
+     */
+    bool _bForceNoRemoteInterface;
+
     /** If set to true, missing subsystem will abort parameterMgr start.
       * If set to false, missing subsystem will fallback on virtual subsystem.
       */