Post with some info about some of the problems/bugs in ExternalInterface: http://codinginparadise.org/weblog/2006/02/how-to-speed-up-flash-8s.html
"In general, whoever coded ExternalInterface should be fired. Great idea, terrible implementation. Have they ever heard of unit tests and boundary conditions?" -David R On 6/13/06, Lee McColl-Sylvester <[EMAIL PROTECTED]> wrote:
Not really, just create an ArrayToString parser function :) Lee -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 13 June 2006 15:11 To: Flashcoders mailing list Subject: RE: [Flashcoders] externalInterface Issue Yeah sending it in chunks is an option but that requires more from the backend. A friend of mine just explained that it probably had to do with Firefox being able to directly communicate with the plugin which would make it lightningfast...and IE doesnt do this which makes it slower. // joakim > As an actual helpful reply, you could always try cutting the string down > and then send the string in separate vars. Actually, have you tried > sending the thing cut up into an Array? You could always do a join() on > the other side. > > Lee > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: 13 June 2006 14:50 > To: flashcoders@chattyfig.figleaf.com > Subject: [Flashcoders] externalInterface Issue > > Are there any known limitations when using the ExternalInterface to send > large amounts of data. > > I set up this example and I'm not liking the result. > > 1. Code in flash > import flash.external.ExternalInterface; > ExternalInterface.call("receiveData",massiveString); > > > 2. Code on htmlpage > function receiveData(args) { > > alert("result: " + args.colorData.length); > return args.colorData.length; > > } > > Firefox and Internet Explorer obviously treats this differently. While > Firefox communicates with flash almost instantly and sends the string > with > minimal delay Internet Explorer times out when the string gets to big. > > So my question is > How come the two browsers handles this differently and how could i work > around it so that i can send that massive string. > > Thanks, > > joakim > > _______________________________________________ > Flashcoders@chattyfig.figleaf.com > 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 > _______________________________________________ > Flashcoders@chattyfig.figleaf.com > 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 > _______________________________________________ Flashcoders@chattyfig.figleaf.com 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 _______________________________________________ Flashcoders@chattyfig.figleaf.com 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
_______________________________________________ Flashcoders@chattyfig.figleaf.com 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
