summaryrefslogtreecommitdiffstats
path: root/bindings
diff options
context:
space:
mode:
authorDavid Wagner <david.wagner@intel.com>2015-01-16 16:59:06 +0100
committerDavid Wagner <david.wagner@intel.com>2015-01-28 20:02:52 +0100
commit962ff7b523d81249dfc1eb6870b7a6249893e2ea (patch)
treeded0b501ce65c97eefb195bf7b3d896d6f289367 /bindings
parente6711f76f6baaccf449e85b2105fc0e64b20ab9a (diff)
downloadexternal_parameter-framework-962ff7b523d81249dfc1eb6870b7a6249893e2ea.zip
external_parameter-framework-962ff7b523d81249dfc1eb6870b7a6249893e2ea.tar.gz
external_parameter-framework-962ff7b523d81249dfc1eb6870b7a6249893e2ea.tar.bz2
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>
Diffstat (limited to 'bindings')
-rw-r--r--bindings/python/pfw.i3
1 files changed, 3 insertions, 0 deletions
diff --git a/bindings/python/pfw.i b/bindings/python/pfw.i
index da01cdc..ce27173 100644
--- a/bindings/python/pfw.i
+++ b/bindings/python/pfw.i
@@ -88,6 +88,9 @@ public:
// Configuration application
void applyConfigurations();
+ bool getForceNoRemoteInterface() const;
+ void setForceNoRemoteInterface(bool bForceNoRemoteInterface);
+
void setFailureOnMissingSubsystem(bool bFail);
bool getFailureOnMissingSubsystem() const;