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
Should the backend have a mapper (in plugins) from a sender to native format, or should the sender send native format, or should there be a glue service that translates from sender's format to the backend's native format?
The text was updated successfully, but these errors were encountered:
As discussed yesterday, I think we should move as much of the service-specific logic into glue services. Most alert sources will need some glue service to dispatch their alerts into AAS, and it would be easier for third parties to maintain their own code in that way, rather than attempting to get more plugin code into the AAS codebase.
Should the backend have a mapper (in plugins) from a sender to native format, or should the sender send native format, or should there be a glue service that translates from sender's format to the backend's native format?
The text was updated successfully, but these errors were encountered: