Add a file in the NetworkProtocol domain/model. It will expose methods that provide the interface for interacting with a NetworkProtocol. This used to exist, but the re-implementation should focus on more granular functionality within the NetworkProtocol handler. For instance, a NeworkProtocol handler should not have a "pullNetwork" or "pullApplications" method. These methods would be exposed in the NetworkProtocol model, and then the model would orchestrate the sequence of steps. This way there will be less redundant logic in the NetworkProtocol handlers, and the data can be better verified by LPWAN. NetworkProtocol handler methods should be small, and they should receive all the data they need, without having access to the models.
Add a file in the NetworkProtocol domain/model. It will expose methods that provide the interface for interacting with a NetworkProtocol. This used to exist, but the re-implementation should focus on more granular functionality within the NetworkProtocol handler. For instance, a NeworkProtocol handler should not have a "pullNetwork" or "pullApplications" method. These methods would be exposed in the NetworkProtocol model, and then the model would orchestrate the sequence of steps. This way there will be less redundant logic in the NetworkProtocol handlers, and the data can be better verified by LPWAN. NetworkProtocol handler methods should be small, and they should receive all the data they need, without having access to the models.