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, 16 insertions, 0 deletions

diff --git a/parameter/ParameterMgr.cpp b/parameter/ParameterMgr.cpp
index 1d77666..4b8bdf6 100644
--- a/parameter/ParameterMgr.cpp
+++ b/parameter/ParameterMgr.cpp
@@ -306,6 +306,7 @@ CParameterMgr::CParameterMgr(const string& strConfigurationFilePath) :
     _uiMaxCommandUsageLength(0),
     _pLogger(NULL),
     _uiLogDepth(0),
+    _bForceNoRemoteInterface(false),
     _bFailOnMissingSubsystem(true),
     _bFailOnFailedSettingsLoad(true),
     _bValidateSchemasOnStart(false)
@@ -2426,11 +2427,26 @@ void CParameterMgr::feedElementLibraries()
     _pElementLibrarySet->addElementLibrary(pParameterConfigurationLibrary);
 }
 
+bool CParameterMgr::getForceNoRemoteInterface() const
+{
+    return _bForceNoRemoteInterface;
+}
+
+void CParameterMgr::setForceNoRemoteInterface(bool bForceNoRemoteInterface)
+{
+    _bForceNoRemoteInterface = bForceNoRemoteInterface;
+}
+
 // Remote Processor Server connection handling
 bool CParameterMgr::handleRemoteProcessingInterface(string& strError)
 {
     CAutoLog autoLog(this, "Handling remote processing interface");
 
+    if (_bForceNoRemoteInterface) {
+        // The user requested not to start the remote interface
+        return true;
+    }
+
     // Start server if tuning allowed
     if (getConstFrameworkConfiguration()->isTuningAllowed()) {