RE: [Junk E-Mail - LOW] [flexcoders] Re: Choice of backend systems - which provides best functionality
Bob- Web Services / HTTP services are not built to be the primary backend of your flex applications. Because they are XML based, they have quite a bit more overhead than flex's built-in AMF (Action Message Format). AMF is smaller, faster and uses less bandwidth than XML. AMF is what FDS and ColdFusion 7.0.2 use to communicate to a Flex app. So let's say that your question is narrowed down to "FDS or CF?". Adobe's ideal answer is "yes." They are complimentary to each other, CF allows for wonderful rapid development of Flex apps, and FDS brings some amazing features to the table through it's Messaging an Data Management services. Web Services (SOAP) support is in Flex primarily to consume third-party data, allowing you to add it to your app. Hope this points you in the right direction. Shan From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of rhlarochelleSent: Tuesday, August 22, 2006 10:27 AMTo: flexcoders@yahoogroups.comSubject: [Junk E-Mail - LOW] [flexcoders] Re: Choice of backend systems - which provides best functionality Franck,I appreciate your respons. When you say Remote Objects/Flex DataServices provides the most advanced way of interoperating with thebackend, what specifically is possible?What are the capabilities that I would get leveraging RemoteObjects/Flex Data Services that I would not get (or would be difficultto implement) with Web services or HTTP services. If there areresources on the Adobe site that spell this out, please point me to them.Since we are looking at the different possibilities and we havesomewhat of a blank slate, the more I can go into this with open eyesthe better. I appreciate everyone who responded being willing to guidesomeone new to this architecture.Thanks,Bob--- In [EMAIL PROTECTED]ups.com, "Franck de Bruijn"franck.de.bruijn@... wrote: 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 fixit. 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: [EMAIL PROTECTED]ups.com [mailto:[EMAIL PROTECTED]ups.com] On Behalf Of rhlarochelle Sent: Tuesday, August 22, 2006 1:47 AM To: [EMAIL PROTECTED]ups.com Subject: [flexcoders] Choice of backend systems - which provides best functionalityI 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? --No virus found in this incoming message.Checked by AVG Free Edition.Version: 7.1.405 / Virus Database: 268.11.4 - Release Date: 8/21/2006 __._,_.___ -- 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. __,_._,___ -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.4 - Release Date: 8/21/2006
Re: [Junk E-Mail - LOW] [flexcoders] Re: Choice of backend systems - which provides best functionality
On 8/22/06, Shannon Hicks [EMAIL PROTECTED] wrote: Bob- Web Services / HTTP services are not built to be the primary backend of your flex applications. Because they are XML based, they have quite a bit more overhead than flex's built-in AMF (Action Message Format). AMF is smaller, faster and uses less bandwidth than XML. AMF is what FDS and ColdFusion 7.0.2 use to communicate to a Flex app.Does Adobe have any stats on this? Was wondering as I found otherwise in a simple testcopy paste from a old thread: old thread here...but...I just built a example app for my team here to share some Flex luv. Its a simple plain-jane datagrid populated with 500 rows from a database. I made three versions of the app:1) Using remoteobject and typed objects CFC to AS. 2) Using a REST call to return XML via a HTTPService3) Using a WebService to return untyped objects, Structs.#2 whipped the pants off 1 and was a bit faster then 3. I was really expecting 1 to be faster with all the AMF talk and all. I suppose 1 has a bit of over head on bith ends though to handle the objects. So let's say that your question is narrowed down to FDS or CF?. Adobe's ideal answer is yes. They are complimentary to each other, CF allows for wonderful rapid development of Flex apps, and FDS brings some amazing features to the table through it's Messaging an Data Management services. Web Services (SOAP) support is in Flex primarily to consume third-party data, allowing you to add it to your app. Hope this points you in the right direction. Shan From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of rhlarochelleSent: Tuesday, August 22, 2006 10:27 AMTo: flexcoders@yahoogroups.comSubject: [Junk E-Mail - LOW] [flexcoders] Re: Choice of backend systems - which provides best functionality Franck,I appreciate your respons. When you say Remote Objects/Flex DataServices provides the most advanced way of interoperating with thebackend, what specifically is possible?What are the capabilities that I would get leveraging RemoteObjects/Flex Data Services that I would not get (or would be difficultto implement) with Web services or HTTP services. If there areresources on the Adobe site that spell this out, please point me to them.Since we are looking at the different possibilities and we havesomewhat of a blank slate, the more I can go into this with open eyesthe better. I appreciate everyone who responded being willing to guidesomeone new to this architecture.Thanks,Bob--- In flexcoders@yahoogroups.com, Franck de Bruijn[EMAIL PROTECTED] wrote: 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 fixit. 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 functionalityI 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? --No virus found in this incoming message.Checked by AVG Free Edition.Version: 7.1.405 / Virus Database: 268.11.4 - Release Date: 8/21/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.4 - Release Date: 8/21/2006 -- Douglas Knudsenhttp://www.cubicleman.comthis is my signature, like it? __._,_.___ -- 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"
Re: [Junk E-Mail - LOW] [flexcoders] Re: Choice of backend systems - which provides best functionality
yes, what Franck and Shannon said. :) Honestly, I think we all work in wholly different areas, sectors, ways, and company cultures. One shop may have a clear delineation between front and back end developers and trust only Java on the back and WS/REST calls only. Another shop may not have such a clear delineation and use Remoting with CF only, another may use Cairngorm, another laugh at the word, etc, etc.. So really it all depends on the job at hand as well as where you are in a company or not, and may very well all depend on whom the IT Director played golf with last week. Personally I totally like the magik of RemoteObject, its just freakin kewl the way it works and keeps your model contiguous between the front/back. I see WebServices for use in exposing your stuff API style to 3rd parties. If you are building a tool that will 100% guaranteed never expose itself, no need for a WebServices trench coat to march around in, eh? ;) 99.9% of the apps I work on are this case. DKOn 8/22/06, Shannon Hicks [EMAIL PROTECTED] wrote: Bob- Web Services / HTTP services are not built to be the primary backend of your flex applications. Because they are XML based, they have quite a bit more overhead than flex's built-in AMF (Action Message Format). AMF is smaller, faster and uses less bandwidth than XML. AMF is what FDS and ColdFusion 7.0.2 use to communicate to a Flex app. So let's say that your question is narrowed down to FDS or CF?. Adobe's ideal answer is yes. They are complimentary to each other, CF allows for wonderful rapid development of Flex apps, and FDS brings some amazing features to the table through it's Messaging an Data Management services. Web Services (SOAP) support is in Flex primarily to consume third-party data, allowing you to add it to your app. Hope this points you in the right direction. Shan From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of rhlarochelleSent: Tuesday, August 22, 2006 10:27 AMTo: flexcoders@yahoogroups.comSubject: [Junk E-Mail - LOW] [flexcoders] Re: Choice of backend systems - which provides best functionality Franck,I appreciate your respons. When you say Remote Objects/Flex DataServices provides the most advanced way of interoperating with thebackend, what specifically is possible?What are the capabilities that I would get leveraging RemoteObjects/Flex Data Services that I would not get (or would be difficultto implement) with Web services or HTTP services. If there areresources on the Adobe site that spell this out, please point me to them.Since we are looking at the different possibilities and we havesomewhat of a blank slate, the more I can go into this with open eyesthe better. I appreciate everyone who responded being willing to guidesomeone new to this architecture.Thanks,Bob--- In flexcoders@yahoogroups.com, Franck de Bruijn[EMAIL PROTECTED] wrote: 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 fixit. 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 functionalityI 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? --No virus found in this incoming message.Checked by AVG Free Edition.Version: 7.1.405 / Virus Database: 268.11.4 - Release Date: 8/21/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.4 - Release Date: 8/21/2006 -- Douglas Knudsenhttp://www.cubicleman.comthis is my signature, like it? __._,_.___ -- 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 Software development tool Software development Software
