Hi Piero, I would

rv49649 — Mon, 28 Jan 2008 03:19:49 -0500

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."

RIA Zone - Comments for "A sketch of Adobe Flex Architecture capabilities"

Hi Piero, I would