Question: The spec talks about "modules". Are these merely functions that can be activated/deactivated via Config, or is a modular structure of the app really meant here?
Thorsten: In principle, we strongly expect that the individual services (paths) of an application are implemented so independently of each other that they can be added, replaced and removed individually without impairing the function of the implementations of another services (paths).
In this sense, a service (path) represents a function and an application represents a vehicle for administrating a set of functions.
Due to the size of the AIPS, we decided to group services (paths) that only make sense in combination. These groups we named modules.
It is currently not planned to activate/deactivate services (paths) by settings in the CONFIGfile.
Question: The spec talks about "modules". Are these merely functions that can be activated/deactivated via Config, or is a modular structure of the app really meant here?
Thorsten: In principle, we strongly expect that the individual services (paths) of an application are implemented so independently of each other that they can be added, replaced and removed individually without impairing the function of the implementations of another services (paths).
In this sense, a service (path) represents a function and an application represents a vehicle for administrating a set of functions.
Due to the size of the AIPS, we decided to group services (paths) that only make sense in combination. These groups we named modules.
It is currently not planned to activate/deactivate services (paths) by settings in the CONFIGfile.