it.
Jason
-Message d'origine-
De : flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] la
part de jeremy lu
Envoyé : mercredi 3 mai 2006 03:09
À : flexcoders@yahoogroups.com
Objet : Re: [flexcoders] Server-Side Architecture for Flex App
For any others such as .Net and PHP you
The Flex server is built on Java and I
think that Flex was originally developed to integrate the most efficiently with
Java.
That would be my choice.
--Kelly
From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Clarke Bishop
Sent:
|
| | |
|-+-
-|
| |
| To: flexcoders@yahoogroups.com |
| cc: |
| Subject: RE: [flexcoders] Server-Side Architecture for Flex App
: [flexcoders]
Server-Side Architecture for Flex App
I would add that this can
be seen in terms of portability, performance and
how much knowledge exist in your company in certain technology. Java will
give the greatest portability, it would run seemly in Windows shops as in
Unix shops
a advantage to RemoteObject use Steven Webster mentioned in the Adobe article on cairngorm was the fact that you can synch your objects between middle-ware and client AS, keeping your model nice and tidy. You can use webservices to return complex custom objects, but can Flash discern these?
- Is there another backend technology I
should be considering?
Are you going to consider Ruby on
Rails as a backend. Its free and makes an excellent backend to
Flex. See here:
http://www.liverail.net/articles/2006/04/16/rubyonrails-1-1-and-flex-2-0-pt-1
For example this line
For any others such as .Net and PHP you will need touse HTTPService or WebService. Consider that your choice mightrun slower
than others.
just one correction,
you can always use NetConnection to connect to any AMF gateway (ie: amfphp, fluorine for .NET) instead of RemoteObject.
--
7 matches
Mail list logo
