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:
“It’s important for parents to watch for trouble and convey to their daughters that, if it comes, they are strong enough to deal with it. Parents who send their [adolescent] daughters the message that they’ll be overwhelmed by problems aren’t likely to hear what’s really happening.”
—Mary Pipher (20th century)
“New York ... is a city of geometric heights, a petrified desert of grids and lattices, an inferno of greenish abstraction under a flat sky, a real Metropolis from which man is absent by his very accumulation.”
—Roland Barthes (1915–1980)