Flash large ActionScript programming experiences

Programming with action script RIA Development has also been a long time. This paper mainly talks about the experience and ideas of the data interaction of the flash RIA architecture.

At the very beginning, it is the flash+xml way to interact with. This approach is now common, but it's too low-level. It is tolerable to develop systems that are less than 50 tables. But if you develop a large system. Each time the data interaction must write the corresponding tagging and parsing the label, wrote the Xml2table effect is not good. It's too complicated. Sensory development has become a complete manual labor.

Later, the development of flash remoting and Axis Web services was started, and manual labor was finally over. However, feel the efficiency of flash remoting some [binary data]. Between system openness and system efficiency I chose the system efficiency.
Another reason is that axis is easy to release under JBuilder. But Eclipse did not find such a good plug-in, hand-deployed. And I don't have a cold for jbuilder. So favor the simplicity of remoting.

In the client's data interaction, at the very beginning, remoting provides a recordset,dataglue, you can bind to the various controls in the MM, this seems to be a very efficient development, but also the way mm respected. But there are also problems with development:

The 1 mm V2 control is a sheer volume killer [SWF volume is rapidly growing].
2 with the dataset provided by MM, the server side is required to provide a dataset that does not account for the connection, this dataset should be similar to those provided by ASP.net

DataTable, and it can be compatible with XML-formatted datasets, and only one of the most common JDBC resultset,rowset is unsatisfactory. I used to develop one of these datasets myself, but on Sun I said jdbc4.0 was coming out. I will endure it. But 2 years have passed and still haven't come out.

And then my solution was:

1 Our team has developed a set of controls to replace the controls for MM.
2 wrote Datatable,xml2table,xml2object and other dataset classes to interact.

This time, however, the dataset I wrote did not get much application. Because we immediately adopted the hibernate. On the client side, we also write the corresponding Pojo as class. Therefore, the client is facing the object, not table,array,item these things. In this way, finally solved the problem has been long, server-side and the client is basically completely oo, the whole of a C/s development mode. Large programs can be developed in a systematic way.

Our final architecture:

FLASH:MVC (M:as DAO; V:uiobject; C[system logic])
Java:remote inferface+ Business logic+ orm+db

Of course, because of the speed of the consideration. Some places are not as pure oo as hibernate. or the dirty way. Of course, project development is the case. Balance is better than perfect, maybe you can use Ibatis later.

Again, I am not optimistic about Laszlo and Flex, he let web development back to the JSP era. Overall, struts,webwork is not immediately applied to the flash RIA. And from the point of view of Longhorn, there is no C/s and b/C, only B/s is.