MACROMEDIA COLDFUSION MX 7.0.2-USING COLDFUSION MX WITH FLEX 2 Guia do Utilizador Página 73

  • Descarregar
  • Adicionar aos meus manuais
  • Imprimir
  • Página
    / 256
  • Índice
  • MARCADORES
  • Avaliado. / 5. Com base em avaliações de clientes
Vista de página 72
About Flex Data Management Service 73
About the Flex Message Service
The Flex Message Service is based on established messaging standards and terminology. The
Flex Message Service provides a client-side API and a corresponding server-side message
service for creating Flex messaging applications. The Message Service also enables
participation in Java Message Service (JMS) messaging.
Messaging systems let separate applications communicate asynchronously as peers by passing
packets of data called messages back and forth through a message service. A message is usually
composed of a header and a body. The header contains an identifier and routing information.
The body contains application data.
Applications that send messages are called producers. Applications that receive messages are
called consumers. In most messaging systems, producers and consumers do not need to know
anything about each other. Producers send messages to specific message destinations, and the
message service routes the messages to the appropriate consumers.
A message channel connects producers and consumers to message destinations. To send
messages over a particular channel, an application connects to the message endpoint
associated with the message channel. A message endpoint is the code responsible for encoding
data into messages, and decoding messages into a format that consumers can use. In some
messaging systems, an endpoint can pass decoded messages to a message broker, which routes
them to appropriate destinations.
A message adapter is code that acts as a conduit between the Flex Message Service and other
messaging systems. For example, the Java Message Service (JMS) adapter is a message adapter
that lets Flex applications subscribe to JMS topics and queues. This adapter lets a pure Java
JMS message application share the same destination as a Flex application; Java applications
can publish messages to Flex and Java code can respond to messages that Flex applications
send.
The following example shows the flow of data from a message producer to a message
consumer. Data is encoded as a message and sent over a channel to a destination. The message
is then sent over a channel to the message consumer and decoded into data that the consumer
can use.
Message producer in
Flex client application
Message consumer in
Flex client application
Message flow
Data
Channel
Destination
Channel
Data
Vista de página 72
1 2 ... 68 69 70 71 72 73 74 75 76 77 78 ... 255 256

Comentários a estes Manuais

Sem comentários