development/examples/api_enable_services - explain the use of invokeInterfaceRegistration to plugin interfaces when applicable.

1 year ago · 9434789845
parent 14077164d7
commit 9434789845
2 changed files with 9 additions and 3 deletions
--- a/source/development/backend/legacy.rst
+++ b/source/development/backend/legacy.rst
@ -1,6 +1,6 @@
-====================
-Using legacy plugins
-====================
+============================
+Using (legacy) plugins
+============================

 -------
 General
--- 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 </development/backend/legacy>`, 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
 ---------------------------------