Flex Messaging system provides asynchronous communication between peers by passing messages back and forth through a Message Service.
A message usually consists of a header and a body. The header contains an identifier and routing information (see also message selectors). The body contains the application data.
Applications that send messages are called producers (please note a producer can be the .NET application too).
Applications that receive messages are called consumers.
Producers send messages to specific message destinations and the Message Service routes the messages to the appropriate consumers.
Message service adapters bridge Flex destinations to back-end systems. Service adapters are designed to be extensible so you can provide your own adapter implementations. A custom messaging adapter has the ability to control how messages are routed.
FluorineFx.Messaging.Services.Messaging.MessagingAdapter is the base class for publish/subscribe messaging adapters. You should extend this class if you want to implement your own messaging adapter.
Custom messaging adapters will provide an implementation for the Invoke method (call the base class implementation to send the message to all clients connected to the server).