A sketch of Adobe Flex Architecture capabilities
Submitted by Piero Campanelli on Thu, 2008/01/24 - 10:31am.
Tags:
I am evaluating Adobe Flex technology to do rich internet applications. Sometimes a picture is worth a thousand words: so in the following I sketched an overview of Flex programming capabilities.
Diagram focuses on how to create a Flash Application (compiling MXML and Actionscript files using the free Flex SDK) and on what kind of interactions a Flex-made application can perform with external systems.
Some starting (and incomplete) references:
- Protocols
- Project & Products
[Source: Piero Campanelli]
- Login or register to post comments
- 1358 reads
- Flag as offensive
- Printer-friendly version
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)
Comments
Roger Voss replied on Mon, 2008/01/28 - 3:19am
Hi Piero,
I would suggest that the open sourcing of BlazeDS constitutes a third i/o interaction branch that is Comet Pattern, and in particular, the long polling technique. This will support server-side push event/messaging and asynchronous remote method invocation. Marhsaling of objects to and from ActionScript3 and Java is likewise supported.
Also, perhaps it would be worth clarifying that Flex i/o interactions are asynchronous, i.e., is similar to programming XmlHttpRequest that AJAX applications make use of. A Flex app, when doing HTTP interactions, is AJAX all the time.
When using Flex HttpService, can do really basic web service interactions by just doing, say, HTTP POST. There is also XmlSocket messaging, but that uses non HTTP interacton over TCP/IP. Can be used for doing server-side push event/messaging, though.
That's a good diagram for new-comer developers to start understanding what a Flex-based RIA app is like. Thanks.
--RogerV
"Let me get right to it by lobbing some grenades: I recognize two arch evils in the software universe – synchronous RPC and remoted interfaces of distributed objects."