Why I picked Flex and not JSP / JSF
• Flex and JSP applications interact effectively with the browser caching mechanism to eliminate redundant loading of resources from the client.
• Flex applications are delivered as complete, self-contained applications, while JSP applications generally require a round trip to the server to generate the next page of the application. These architectural differences have the following performance-related implications:
o Flex applications generally require a larger initial download than the same JSP application, but the Flex application has a faster perceived performance once it is loaded because it runs completely on the local client.
o Flex applications require a single network connection to deliver the entire application, while JSP applications require a new network connection for each new page. Creating network connections is the most expensive portion of network communication. Reduced network connections yield reduced load on the server.
o The client-side logic in the Flex application provides opportunities for optimizing the application and reducing load on the server. For example, for the MXML version of the Flex Store application, you could embed the product images within the application to reduce the number of network connections. The Flex client-side processing model enables the developer to develop specialized mechanisms to achieve optimum performance, including embedding data within the SWF file, progressively downloading and disclosing information on demand, and caching frequently used data after it is downloaded.
o The server CPU load for Flex applications scales with the number of simultaneous downloads and requests for data services, while the number of simultaneous users binds CPU load for JSP applications. Specific applications have different performance profiles, but Flex applications generally require a smaller CPU load than a similar JSP application.
•The Flex server completed more transactions because the application required fewer server connections.
• Flex and JSP applications interact effectively with the browser caching mechanism to eliminate redundant loading of resources from the client. • Flex applications are delivered as complete, self-contained applications, while JSP applications generally require a round trip to the server to generate the next page of the application. These architectural differences have the following…