You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An LPC/LPP server component (actor "Controllable System") needs to provide a measurementId to a limit. If those are not supported, an unused measurement ID should be used and hope that the opposite site doesn't check for validity of the provided ID.
To automate this, the LPC/LPP usecases should be initialized AFTER MPC and MGCP by the application. Then the use case implementation can check for such an ID automatically and use it.
So either the application has the responsibility to do this right, or we change the way usecases are added. An option would be to add all usecases in a single step instead of individually, and there this kind of logic can be implemented.
The text was updated successfully, but these errors were encountered:
An LPC/LPP server component (actor "Controllable System") needs to provide a measurementId to a limit. If those are not supported, an unused measurement ID should be used and hope that the opposite site doesn't check for validity of the provided ID.
To automate this, the LPC/LPP usecases should be initialized AFTER MPC and MGCP by the application. Then the use case implementation can check for such an ID automatically and use it.
So either the application has the responsibility to do this right, or we change the way usecases are added. An option would be to add all usecases in a single step instead of individually, and there this kind of logic can be implemented.
The text was updated successfully, but these errors were encountered: