I should probably give people an update on this. I got pretty stuck when I hit this bug here: http://www.compoundtheory.com/?action=displayPost&ID=384
As it pretty much completely destroyed the possibility of doing Flex/Transfer communication the way I * thought * the easiest way was going to be. That being said, the end result of be digging through layers of Remoting, AMF and BlazeDS stuff, is a product called Conduit, that will enable Transfer to do some pretty seamless integration with Flex, without any of the AOP / Translation CFCs. You can read more about Conduit here: http://www.compoundtheory.com/?action=displayPost&ID=385 So you can pretty much ignore some of the earlier stuff (except the generation code part, that stays), and expect something rather different in the future. Mark On Sat, Nov 29, 2008 at 10:27 AM, Mark Mandel <mark.man...@gmail.com> wrote: > Awesome, so it should get a good workout! Wonderful ;o) > > So there are several layers to what I am doing with Flex integration, > so I'll give you the big picture.... -- E: mark.man...@gmail.com W: www.compoundtheory.com --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to transfer-dev@googlegroups.com To unsubscribe from this group, send email to transfer-dev-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
