This content has been marked as final. Show 3 replies
Consider the alternative: you develop a site with dynamic pages using JSP, ASP, etc. During the course of your application's use, your server is being hit time and time again for pages, probably going into the database, then assembling a page using that data and sending it off to the client. Then on the client the HTML has to be digested and formatted by the browser.
With Flex, your customers hit the server, get the HTML wrapper page and download the 300K SWF. After that, requests for data make your server query the database, but then that data is delivered back to the Flex client with far less overhead since the server does very little after that. Plus you are generally transmitting just the data (in XML, or as binary AMF objects) back to the client.
About two years ago we did a serious performance benchmark between Flex and JSP. While the initial Flex download was greater than the first JSP page, after that Flex put a lot less stress on the server.
I am wandering if the SWF file inside html wrapper will save into customers browser catch when it gets the first time hit, so that customers will need not to download it again and again after they close the browser and reopen it ,or restart their PC. Is it the usually case?
The SWF may be cached by the browser.