Message Abstraction
To provide implementation language and message transport independence all operations of a service must be defined by a language/platform/encoding agnostic specification. The MAL defines this set of basic data types and how they must be used to build up the messages that make up the operations of a service. This only then has to be mapped once, in an MO standard, to a specific implementation language or transport encoding to apply to all services that are defined in terms of the MAL. In addition to the patterns of interaction and the abstract API the MAL provides support for the following: – generic concepts, such as domain, session and zone; – generic facilities such as access control (authentication and authorisation) and Quality of Service.
Read more about this topic: Message Abstraction Layer
Famous quotes containing the words message and/or abstraction:
“What’s the use? She would only want me to take a message to dear Albert.”
—Benjamin Disraeli (1804–1881)
“Before abstraction everything is one, but one like chaos; after abstraction everything is united again, but this union is a free binding of autonomous, self-determined beings. Out of a mob a society has developed, chaos has been transformed into a manifold world.”
—Novalis [Friedrich Von Hardenberg] (1772–1801)