Summary
After reading this chapter, you should have a pretty good understanding of how the process of message customization works in the Flex messaging world. Now roll up your sleeves and see if you can improve the reliability of messages in your application.
Have you noticed that this effort is done in the objects that support the messaging layer, and your application developers don’t need to worry about message acknowledgment or out-of-sequence messages in their code? This is the main theme of the entire book: make application developers write less code. We’ll keep repeating this mantra in every applicable situation—in the least annoying way possible, of course.
The source code of this chapter comes as two projects:
A combined Flex/Java project, com.farata.rtmp.components.demo (in real-world projects, it’s better to separate Java and Flex code into two projects)
The Flex library project com.farata.rtmp.components
But those projects come with a disclaimer: the code used in this chapter is written for illustration purposes only. Although it’s conceptually correct, don’t treat it as a production-ready solution. We urge you to analyze all specific situations that may arise in your business application and provide their proper processing in custom channels, adapters, and endpoints.
Get Agile Enterprise Application Development with Flex now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
