Adobe opens source BlazeDS
The company Adobe has reported good news, which will certainly please developers on the Flex platform. In the very near future, the source code for BlazeDS, a high-performance data transfer technology between Flex applications and backend servers, will be published. Sources will be published in early 2008 under the completely liberal LGPL v3 license.
In addition, Adobe has already published detailed specifications ( PDF ) for the binary data transfer protocol Action Message Format (AMF), which serves as a transport for BlazeDS services. The AMF protocol was first introduced in 2001 along with Flash Player 6, and now it is no longer so relevant. However, Adobe is clearly trying to encourage developers to use this technology.
According to experts, the availability of documentation can expand the scope of AMF even in web applications in languages that are not supported by Adobe. In other words, it became possible to combine Flex-applications on the website with the existing backend infrastructure, regardless of what programming language it is in. For example, you can create a subclass of Python Pickler that will directly transfer data via AMF.
One of the most important features of BlazeDS is to support persistent connections. This is an advantage over Ajax applications that have to constantly query the server, usually at random intervals or when user activity appears in order to get new data. At the same time, BlazeDS allows you to send data directly to the client, which potentially increases the speed of such applications. A similar mechanism for Ajax is incorporated in the specifications of Serer-Sent Events , but they are now implemented only in the Opera browser.
')
This is not the first time that Adobe has opened one of the most important components of its web platform. The ActionScript virtual machine source as well as the Flex SDK and the compiler have already been published. Although Flash Player, RTMP protocol, and other critical components are stored under seven locks, the company clearly recognized the need to become more open and friendly to the developer community.
True, some knowledgeable people claim that Adobe was forced to open AMF, because this protocol was hacked and illegally documented in the framework of the AMFPHP project. So the copyright holder simply approved the de jure state of affairs, which happened de facto.
via Ars Technica
In addition, Adobe has already published detailed specifications ( PDF ) for the binary data transfer protocol Action Message Format (AMF), which serves as a transport for BlazeDS services. The AMF protocol was first introduced in 2001 along with Flash Player 6, and now it is no longer so relevant. However, Adobe is clearly trying to encourage developers to use this technology.
According to experts, the availability of documentation can expand the scope of AMF even in web applications in languages that are not supported by Adobe. In other words, it became possible to combine Flex-applications on the website with the existing backend infrastructure, regardless of what programming language it is in. For example, you can create a subclass of Python Pickler that will directly transfer data via AMF.
One of the most important features of BlazeDS is to support persistent connections. This is an advantage over Ajax applications that have to constantly query the server, usually at random intervals or when user activity appears in order to get new data. At the same time, BlazeDS allows you to send data directly to the client, which potentially increases the speed of such applications. A similar mechanism for Ajax is incorporated in the specifications of Serer-Sent Events , but they are now implemented only in the Opera browser.
')
This is not the first time that Adobe has opened one of the most important components of its web platform. The ActionScript virtual machine source as well as the Flex SDK and the compiler have already been published. Although Flash Player, RTMP protocol, and other critical components are stored under seven locks, the company clearly recognized the need to become more open and friendly to the developer community.
True, some knowledgeable people claim that Adobe was forced to open AMF, because this protocol was hacked and illegally documented in the framework of the AMFPHP project. So the copyright holder simply approved the de jure state of affairs, which happened de facto.
via Ars Technica
Source: https://habr.com/ru/post/17671/
All Articles