Home » Software » Adobe Flex
Topic: Adobe Flex
Download (82) times
Last Download at Monday 23rd of April 2012 01:02:45 AM
Capacity Planning for Adobe's Macromedia Flex 1.5
The purpose of this document is to help the reader better estimate what the hardware requirements for Adobe s
Macromedia Flex 1.5 application might be in a production environment.
The document gives an overview of capacity planning, then addresses capacity planning issues specific to Flex.
The document then walks you through the load testing process using a baseline Flex application and presents
performance test results for this application. ...
Flex is a platform for creating rich interfaces for web applications. The Flex server-side application can be
deployed as a standard J2EE web application and is supported on a number of popular J2EE application
servers. Those familiar with the ASP/JSP model understand that in order to produce an HTML page, the server
side code must first gather the necessary data from the business tier, and then embellish that data with HTML
tags which determine how the data is presented. All this translates to server CPU cycles.
Flex departs from this model by providing a client technology (Macromedia Flashâ ¢ from Adobe) for the user
interface, relying on the server solely for the data. The user interface is authored using a text based markup
language (MXML) and compiled into a binary format (SWF). When a user requests an application via an URL, the
SWF file is transferred to the client where it begins to execute. All requests for data are handled by the server and
subsequently transferred to the client. This separation of processing allows the client to handle simple tasks such
as field validation, data formatting, sorting, and filteringâ thus freeing up valuable server CPU cycles.
One of the key features of the Flex server application is its ability to â proxyâ service requests on behalf of the client.
This proxy is similar in nature to an HTTP Web Proxy and is used to handle Web Service and HTTP Service calls
made by Flex clients. The Flex proxy accepts an HTTP Service or Web Service request from the client application. It
then forwards the request to the intended service, waits for a response, and returns the results.
It is possible to bypass the Flex proxy, though it means not taking advantage of the useful services it provides.
The Flex proxy allows your application to access URLs that reside on different domains, adds an additional
layer of security, and provides support for stateful services.
There is some overhead associated with using the Flex proxy. Requests that go through the proxy may take
slightly longer than direct requests. Also, using the proxy will result in additional TCP/IP sockets opened on the
application server machine.
This is to be expected since the Flex server is acting as a web client to the HTTP Service or Web Service . This
is true even if the target service resides on the same machine as the Flex server. It is always recommended that
TCP/IP settings be optimized for the server machine running Flex.
...
Source: www.azavar.com
Related PDF Files
Comments for Capacity Planning for Adobe's Macromedia Flex 1.5