All geek questions in one place

Pros and cons of using BlazeDS or web services as remote access and messaging technology between the Flex view layer and the Spring business layer?

At my company, we are going to use Flex3 for the presentation layer of the new financial web application and Spring for the business layer, but there is still a discussion about the best messaging / remoting technology. Can you share your experience in terms of the pros and cons of using a particular technology?

+3
source share
2 answers

In my experience, use BlazeDS if you don't need to use web services that various technologies can access.

BlazeDS

Pros: less intensive server, less client processing time, less data packet (it is binary), which means that overall a quick call. It can publish / subscribe, as well as call a method.

Cons: Not compatible with external ends of non-Flex (although it's open source, so theoretically it could be.)

Webservices

Pros: well established, almost cross platform. Easy to read and translate problems.

: . XML AS Objects, . XML, ( XML, .)

. .

+6

BlazeDS AMF HTTP. , , , RTMP Adobe LiveCycle ES. LiveCycle , , ( , ).

0

Source: https://habr.com/ru/post/1713523/

More articles:


All Articles