On 9/5/07, Tom Chiverton <[EMAIL PROTECTED]> wrote: > > > > 2. Flex 2 AND database: We have created an XML for the data, that's > makes > > the application sluggish as hell! XML data have much overhead ( I > believe > > something like 2/3 ) > > Yes. And ? > There is a reason ColdFusion talks AMF3 to Flex, not XML REST-style.
+1 here. If you're using CF as the back end, why would you use XML over AMF? > 3. Flex 2 AND performance: On my machine it works ok, but older machines > > it's has serious performance issues. > > Maybe. Cutting out effects if a lot of your client base is on older > hardware > helps. > > > 4. Flex 2 AND filesize: 400 KB for a shoplike application, product and > > filtering! > > That's for the whole app, remember. How much HTML, JavaScript, CSS, images > etc. etc. are there in a typical multi-stage web page ? More than 400K ? I > think so. > > > Instead I would rather programmed it in oldÂstyle Coldfusion HTML with a > > little javascript. > > For really quick things, just data entry for an admin. backend, this makes > sense. > You shouldn't do Flex just because lots of other people are doing it - > maybe > all your clients are using SmartPhones :-) For these kinds of performance issues, look at using Modules. You don't have to have one single, giant Flash file. Modules let you break things up and then only pull in the parts you need at runtime. This makes a HUGE difference in the performance of a Flex app, especially large ones. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Enterprise web applications, build robust, secure scalable apps today - Try it now ColdFusion Today ColdFusion 8 beta - Build next generation apps Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:287818 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
