MACROMEDIA FLASH REMOTING MX-USING FLASH REMOTING FOR FLASH MX 2004 ACTIONSCRIPT 2.0 Spezifikationen PDF herunterladen (Seite 35)

This is the Title of the Book, eMatter Edition

Architecture for Flash Remoting Applications

7. The Flash Player receives the AMF data from the server and deserializes it into a

native ActionScript datatype (in this case a String object). Depending on the data

sent back, the deserialization is done within the Flash Player or the NetServices

code.

8. Finally, the string is returned to an ActionScript callback function specified by

the developer to receive data loaded from the server.

Although a lot happens when a remote service is called from the Flash Player, most

steps are abstracted away from the developer. The developer has only to write the

client-side ActionScript that calls the remote service (Step 1) and receive the response

from the remote service (Step 8). Of course, someone has to write the code for the

remote service itself (Step 5), but that is often done by a different developer or inde-

pendently of Flash, such as in the case where a Flash front end is being added to an

existing web service.

Architecture for Flash Remoting Applications

We conclude this chapter with a general overview of a client/server architecture

using the Flash Player and the Flash Remoting gateway. Generally, Flash/server

applications follow an n-tiered architecture. Figure 1-7 depicts such an architecture,

comprising a client/presentation tier (the Flash Player), a middle tier (Flash Remot-

ing gateway running within an application server), and a data tier (a database, XML

file, or other data source).

Figure 1-7. The Flash/server n-tiered application architecture

Client

Server

Flash Player

Flash Remoting

Application

server

XMLDatabase Other data

source

Presentation

tier

Middle

tier

Data

tier

1 2 ... 30 31 32 33 34 35 36 37 38 39 40

Keine Kommentare

MACROMEDIA FLASH REMOTING MX-USING FLASH REMOTING FOR FLASH MX 2004 ACTIONSCRIPT 2.0 Spezifikationen Seite 35