I don't have full details about changes in each browser version. There are two performance hits described here: (a) running things in a browser (Projectors (and presumably Apollo) are fastest; different browsers have different strategies in allocating processor cycles to plugins); (b) piping the plugin's content to the browser for compositing, rather than directly-to-screen (WMODE).
If your tests show that a particular version of Microsoft Internet Explorer performs much worse than other browsers do, then a good first step is to generalize the observation... confirm it with basic barebones SWF/HTML (no plugin-in-DIV, no rapidfire messaging etc), and confirm it on multiple machines. I haven't heard many people previously report "IE freezes w/WMODE" -- if that were *always* the case then we'd see more of an uproar on the lists. That's what makes me wonder whether there's a particular dependency in this case, that gives you dramatically worse performance than what others see. But there *will* be a performance degradation when playing within a browser, and when asking the browser to blend the plugin's content into its own rendering engine. It shouldn't cause an outright freeze, but there will indeed be a cost to performance. jd _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
