> You are making assumptions. Flash gives you the ability to > do things you couldn't do before in html, which could > required higher bandwidth than the equivalent application > using html. While the extra bandwidth may be worth it for > a better experience, the extra bandwidth is still there.
You are making an invalid comparison. If you're doing something in Flash that you couldn't do in HTML, then the applications aren't really equivalent, are they? > Flash applications do not inherently save bandwidth. No. I would argue that well-written Flash applications tend to be less bandwidth-intensive than well-written HTML-based applications, though. The "document" model of HTML just isn't well-suited for use as an application interface. You can go through contortions of this model to make it more suitable for that use, but you're putting lipstick on a pig, if you know what I mean. I don't think that Flash is the answer to every interface question, but I know for sure that HTML isn't the answer, either. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
