I don't think integrating BlazeDS will be too difficult. You'll definitely
get better performance out of it than if you went with REST or even SOAP.
REST would definitely give you the reusability for other front ends, but
like was stated before you lose out on the ability to use a full fledged
dom
I'm using BlazeDS and AMF for quite a year now, and for me is much more
attractive, because your flex side is completely OO, instead of xml/JSON/WS
parsing related with E4X. Performance is a good argument too, but I believe
for Appfuse, everything must be kept flexible. Not that would be so
difficu
I believe REST is a better option as it can be used by multiple
front-ends and can also be used as an API. However, if you can
convince me that BlazeDS or AMF is a better choice, I'm open to that
as well.
Matt
On Fri, Mar 13, 2009 at 1:35 PM, Rafael Nami wrote:
> Hi Matt, how are you?
> What abo
Hi Matt, how are you?What about the Flex integration - are you thinking on
use REST/WS to communicate with it, or are you thinking on doing that with
BlazeDS and AMF?
Best Regards
Rafael Nami
2009/3/13 Matt Raible
> All,
>
> I've created a wiki page with ideas I have for improving AppFuse as
>
All,
I've created a wiki page with ideas I have for improving AppFuse as
part of Google's Summer of Code. If you have additional ideas, please
add them to this page.
http://appfuse.org/display/APF/Google+Summer+of+Code
For your convenience, I've copied the list below.
* Create a new archet
