RE: [Junk E-Mail - LOW] [flexcoders] Re: Choice of backend systems - which provides best functionality

Tue, 22 Aug 2006 09:14:36 -0700

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 rhlarochelle
Sent: Tuesday, August 22, 2006 10:27 AM
To: flexcoders@yahoogroups.com
Subject: [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 Data
Services provides the most advanced way of interoperating with the
backend, what specifically is possible?

What are the capabilities that I would get leveraging Remote
Objects/Flex Data Services that I would not get (or would be difficult
to implement) with Web services or HTTP services. If there are
resources on the Adobe site that spell this out, please point me to them.

Since we are looking at the different possibilities and we have
somewhat of a blank slate, the more I can go into this with open eyes
the better. I appreciate everyone who responded being willing to guide
someone 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 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: [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
> 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?
>


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



__,_._,___

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

Reply via email to