Open two browser, or two windows of the same browser, or to tabs of same browser or whatever. Then, load there a page with this type of communication between two swf files. And look where the second loaded instance of the page sends the messages. BOTCH.

It seems it is the way they decided to do it. The receiver string identifier must be something that is registered by the adobe player so other swfs can recognize it. But that makes it very very very easy to collide with another localconnections receivers of other swfs (probably many many people would set that string to “connection”, “myconnection”, “conn”…). Then lets look which one receives the messages and from where. Of course there is the domain limitation but even on same domain that can collide.

You can just test with this page. Open it on two tabs of your browser and then click and throw the ball on the second tab. What happens? And as I mention it is not only on same browser if you load page on two different browsers it is the same. This is an example of collision on same domain.

And other example of collision. If I use this on a banner that is shown on all pages of a site if a user opens in its browser two pages of that site (even not same page, just to pages of my site) the second page flash sender would send messages to the first page receiver. That makes no sense at all.

I even tried to use it on a project where the send is almost at the begining of the swf and as soon as the message is received I close the connection and even destroy it (in this project was no more needed). But even that simple one that almost works, fails sometimes. It seems the message is not always sent, or it is delayed by other player tasks, I dont know exactly whats happening but fails. So even that simple one is not 100% working.

I prefer sender to javascript, javascript to receiver that works as it is expected.

I tried creating a code but it didn’t work. It may be a security issue. I tried putting an event listener for each pages but to no avail. Hence, I just created a session variable. Primitive, but it gets the job done. but I was hoping I could use the LocalConnection.

Thanks Again.

I get this error:

ArgumentError: Error #2082: Connect failed because the object is already connected.
at flash.net::LocalConnection/connect()
at Receiver_fla::MainTimeline/frame1()