There is no reason not to use AMF format if you can guarantee that the Flash Remoting gateway is available on the server, as it is in these cases. No hand-written server-side code is necessary. The Flash Remoting adapter on the server takes care of the necessary translation, so your Flash movie can simply use the service. Figure shows a diagram of how Flash Remoting fits into the picture. The Flash client browser makes the request via client-side ActionScript. The ActionScript code refers to the Flash Remoting gateway and the web service. NET, the application server creates the proxy automatically.
The proxy then sends the request to the remote web service. The remote web service responds to the application server with a SOAP envelope.
A Flash-forward look
The Flash Remoting gateway gets the results back from the application server and translates the results into ActionScript objects. The gateway passes the result back to the Flash client. SOAP is a large protocol. It is based in XML and requires major parsing inside of the Flash plugin. Flash Player 6 excluded SOAP support in order to keep the plugin footprint small and accelerate deployment.
The Flash Player has security restrictions that prevent it from loading content from other domains.
This is a good thing, as it keeps the level of acceptance of the Flash player very high; having Flash on your computer is regarded as safe. The AMF format of Flash Remoting is a terse binary format, which results in fast transfer speeds between the Flash Remoting gateway and the Flash movie. Furthermore, there is faster processing because of less serialization and deserialization. You can imagine that, with more complex web services, the savings in bandwidth can be enormous.
There are other techniques to access a web service from Flash, such as parsing the SOAP on the server using server-side code, but Flash Remoting is by far the easiest method to use. This chapter discusses the different implementations of Flash Remoting and how to use web services in each.
Using Flash Remoting for consuming web services is a viable option in many cases; however, there are a few limitations:. At this time, XML web services are not supported. You have to supply all of the parameters to a web service, even if they are optional parameters. Furthermore, because the middle tier might comprise multiple levels, only the middle tier's interface to the data tier needs to be adjusted. By having multiple tiers, each tier can be optimized for its particular task and environment.
This is particularly important when using Flash as the presentation layer, since Flash runs on the client side, which can be a much more variable and unknown environment than the server. For example, you can filter large sets of data in the middle tier where you have a known environment and resources, versus doing it on the client side within Flash where, depending on the client's machine, it might not perform well. In this case, you may want to initially sort the data set on the server and then have any user-initiated sorts occur within the Flash Player. This is a good tradeoff between client-side processing concerns and the extra bandwidth required to transfer data sets to and from the server.
Components such as the DataGrid from Macromedia further abstract the implementation of this logic and allow complex sorting and filtering directly within the Flash movie. I address these topics in subsequent chapters, using examples where appropriate. It is much easier to update the application's core business logic when it is centralized in the middle tier, verses spreading it out across multiple tiers and technologies. Furthermore, keeping business logic out of the presentation tier allows you to test the business logic separate from the presentation tier, isolate any problems, deploy changes, and integrate it with the other tiers of the architecture.
Finally, this multitiered architectural structure mirrors the common divisions of labor during Flash application development. Often, a Flash developer creates the Flash movie and client-side ActionScript, while another developer creates the server-side code.
They can program and test their code independently, making development much easier, faster and less error-prone. Provided that the interfaces between the levels are defined, the Flash developer can use temporary data hardcoded into the application to test the application. The server-side developer simply needs to ensure that his code implements the defined API to the presentation tier. Avoid the temptation to use ActionScript to implement the application's business logic within the Flash movie's presentation layer.
Such an approach ties the Flash movie too closely to the lower levels of the architecture and exposes the business logic on the client side, making the application more difficult to maintain and update, as well as possibly affecting client-side performance adversely. The application server is much better suited for the business logic.
- Operator Theory and Interpolation: International Workshop on Operator Theory and Applications, IWOTA 96!
- Risk-sharing in the Pharmaceutical Industry: The Case of Out-licensing (Contributions to Management Science).
- Books & Videos.
- How to Commercialise Research in Biotechnology?: Effectiveness of the Innovation Process and of Technology Transfer in the Biotechnology Sector.
- Download Flash Remoting: The Definitive Guide PDF - video dailymotion;
Chapter 12 goes into much greater detail about the best practices in building a Flash Remoting application. Later chapters discuss differences specific to additional technologies. Toggle navigation. See also. Home Macromedia Flash remoting. Figure Flash 5 n-tiered application architecture with multilayered middle tier However, using Flash Remoting and Flash Player 6 or later, this logic is handled by the Flash Remoting gateway, sitting on the server atop the middle tier, as shown in Figure N-tiered application architecture with Flash Remoting gateway 1.
N-tiered architecture with data abstraction layer By having multiple tiers, each tier can be optimized for its particular task and environment. Remember the name: eTutorials. Part I: Remoting Fundamentals.
Flash Remoting: The Definitive Guide - PDF Free Download
Chapter 1. Introduction to Flash Remoting. Chapter 2.
Installing, Configuring, and Using Flash Remoting. Chapter 3. Chapter 4. Flash Remoting Internals. Chapter 5. Chapter 6. Server-Side ActionScript. Chapter 7. Flash Remoting and Java. Chapter 8. Flash Remoting and. Chapter 9. Flash Remoting and PHP. Chapter