- managed container
See Fabric Container.
- marshalling
The process of taking in-memory objects and converting them to a binary or textual format for transmission over a transport.
See Also unmarshalling.
- master/slave
A topology in which a single instance, the master, is active and one or more instances, the slaves, are ready to resume when the active instance stops.
- message
messaging—An atomic unit of data that is passed between two or more clients. A message consists of three components:
headers—contain a predefined set of metadata that is used to communicate information about a message between the different parties that handle the message
properties—contain application defined metadata about a message to the different parties that handle the message
body—contains the messages payload
routing—The data passed processed by a route. A message consists of three components:
headers—contain metadata that is used to communicate information about a message between the different processors that handle the message
attachments—contain binary data that is associated with the message
body—contains the messages payload
services—Any data passed between a service provider and a service consumer, or between two endpoints. Messages are defined in using the WSDL
messageelement.See Also fault message, input message, output message.
- message exchange pattern (MEP)
The pattern of messages used by an application. There are two major message exchange patterns:
request-response—one client sends a message and expects a message to be returned
one-way—a client sends a message without expecting a response
The WSDL specification defines a number of more detailed MEPs that are all variations of the two basic patterns.
See Also request-reply pattern.
- message group
A collection of JMS messages that are assigned the same JMSXGroupID.
When used in conjunction with the JMSXGroupSeq message groups can be used to ensure that messages are processed in the proper sequence.
- message selector
A string containing a boolean SQL statement using SQL 92 syntax that is used to select messages based on JMS message header properties.
- middleware
A software communications layer that manages the interaction of disparate applications across heterogeneous hardware and network environments.
 |  | |
 |
