This content has been marked as final. Show 1 reply
"cnunciato" <firstname.lastname@example.org> wrote in message
> Hi there:
> I'm using Flex 3 in the UI of a Windows app (Flash player as an embedded
> ActiveX control), and passing data between them with ExternalInterface
> (primarily into the Flex app, as opposed to out). I'm finding, though,
> the performance is pretty awful, particularly with larger (i.e., custom)
> objects; the more EI calls we make, and the larger the custom objects as
> in, the harder things seem to drop off performance-wise.
> I'm assuming there's a good deal of overhead in serializing these objects,
> I'm wondering, are there any best practices out there for using
> ExternalInterface in this particular way? There doesn't seem to be much
> there in terms of documentation on this subject yet.
> Is it better, say, to pass a large block of XML into the player control as
> string, and parse it with Flex, than to pass it as a custom object, as a
> How should Flex apps requiring a relatively tight integration with their
> apps best use ExternalInterface without sacrificing performance? Is EI
> performance an issue Adobe is addressing? Any implementation differences
> between players 9 and 10? What kinds of things should we avoid to get the
> out of this feature?
This may or may not help, given it was written for Flash 8.
I've found that often a perceived long load is caused by what happens once
you get the data--i.e. the things you need to do to display the state of the
data visually. It may be that you can help by slimming that part down as