From 94347898455523e320fa1d2e98626290303194fb Mon Sep 17 00:00:00 2001 From: Ad Schellevis Date: Thu, 22 Dec 2022 09:59:14 +0100 Subject: [PATCH] development/examples/api_enable_services - explain the use of invokeInterfaceRegistration to plugin interfaces when applicable. --- source/development/backend/legacy.rst | 6 +++--- source/development/examples/api_enable_services.rst | 6 ++++++ 2 files changed, 9 insertions(+), 3 deletions(-) diff --git a/source/development/backend/legacy.rst b/source/development/backend/legacy.rst index 051f00ca..3098e534 100644 --- a/source/development/backend/legacy.rst +++ b/source/development/backend/legacy.rst @@ -1,6 +1,6 @@ -==================== -Using legacy plugins -==================== +============================ +Using (legacy) plugins +============================ ------- General diff --git a/source/development/examples/api_enable_services.rst b/source/development/examples/api_enable_services.rst index 98006d7c..31e9273c 100644 --- a/source/development/examples/api_enable_services.rst +++ b/source/development/examples/api_enable_services.rst @@ -108,6 +108,12 @@ The service above defines the following static variables: The :code:`reconfigureForceRestart` overwrite tells the controller if it should always stop the service before trying a start, some services can be signaled to do a reconfigure without stopping. +.. Tip:: + + When a service may register new :doc:`interfaces `, one could implement the protected method + :code:`invokeInterfaceRegistration` and make it return :code:`true`, after which the plugin system will detect changes to the + interface registrations automatically. + Endpoints ---------------------------------