IN THIS CHAPTER
Understanding the Message Service
Configuring messaging on the server
Using adapters, channels, and destinations
Creating Flex messaging applications
Using producers and consumers
Sending and receiving simple messages
Working with complex messages
Filtering messages on the server
Debugging message traffic
When Flex Data Services 2 was first released, one of its most compellingnew features was known as the Flex Message Service. This service enabled developers to create applications in whichdata and information could be shared instantly between multiple connected client applications without having to program with low-level socket-style application programming interfaces (APIs).
When Flex Data Services was renamed LiveCycle Data Services, this serverbasedfunction became known simply as the Message Service (or, when referred to in the context of BlazeDS, the BlazeDS Message Service). Using this service, Flex client applications send messages to a destination on the server. The server then distributes the messages to other connected clients over a supported communication protocol.
LiveCycle Data Services (referred to here simply as LCDS) supports the Real Time Messaging Protocol (RTMP), a protocol that implements true server-push capability. When LCDS Message Service destinations use an RTMP channel, data is pushed from the server to connected clients instantly (or as close as possible, given available network and server resources). ...