It seems obvious (maybe I'm missing something) that you would not want to exchange messages between Flex clients using the JMS adapter since it would not be required. For communication between external resources and between external resources and Flex clients you could use the JMS adapter since it would be required.
The sample chat application that comes with FDS follows this model. What exactly is your potential concern about this approach? --- In [email protected], "Venu Vasireddy" <[EMAIL PROTECTED]> wrote: > > Hi, > > > > > > I need your opinion regarding one design decision. > > > > Our Flex 2.0 based system needs to exchange messages with external > systems using JMS compliant messaging infrastructure. > > > > My dilemma is either to use "Flex Messaging" or pure J2EE messaging? > > > > I convinced Executive team to use J2EE messaging for external message > exchange and Flex messaging for intra client conversations. > > > > Your opinion is highly regarded. > > > > Thanks > > Venu Vasireddy > > Architect > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
