RE: [flexcoders] Choice of backend systems - which provides best functionality

[Franck de Bruijn]

Flex is supposed to be backend independent. So you should choose the technology you’re most comfortable with.   There are in general 3 ways of integrating with your back-end: webservices: total freedom, but can turn out to be hard. Especially with .Net there are some problems, although Adobe is working to fix it. With Java/Axis, you’ll probably find no issues. Remote Objects / Flex Data Services. The most advanced way of interoperating with your back-end, but requires JAVA on the backend. HTTP services: simple HTTP calls. For simple interfaces it will work, but for the more complex ones it will be insufficient.   Cheers, Franck   From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of rhlarochelle Sent: Tuesday, August 22, 2006 1:47 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] Choice of backend systems - which provides best functionality   I am new to Flex 2, and have the opportunity to develop a new application. Given all of the choices of back end technology out there (J2EE, Coldfusion, PHP), which will provide for the richest user experience? It seems that leveraging J2EE and Java gives the best potential for sharing objects (and updates to objects ) over the wire. Have I got this right? __._,_.___ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com SPONSORED LINKS Web site design development Computer software development Software design and development Macromedia flex Software development best practice YAHOO! GROUPS LINKS  Visit your group "flexcoders" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. __,_._,___