I think I've found a flash bug with the LocalConnection
communication setup, such as described here. The site below is not mine, I'm just using it to show that the problem also occurs on other sites:
How to reproduce:
http://fcontheweb.com/articles/localconnection/
If you open the site in 2 browser windows, find the as3 example that sends a message between 2 as3 components.
Click the button in the first browser window: it will communicate locally with the message box. If you then press the button on the second browser window, nothing will happen. If you close the first browser window, you have to refresh the page before things start working for the second window.
I think this is because the namespace of as3 objects in both windows are overlapping in the flash player plugin of the browser, and the communication channel link is being overwritten.
You can easily verify my hypothesis by opening the 2 windows again, but now press the button in the LAST window first. Nothing will happen in that window, but the message will show up in the first window instead! Somehow, the last page's receiver is not created, because a receiver by that name already exists in the flash plugin's object store.
Can you confirm this, and more interestingly, does anyone have a workaround for this? Would it be possible to detect how many instances of an swf are running locally and use that for the connection name?
Edit: The observed behavior is not a bug, but intended behavior. However my problem still stands: how to have pages inside the same browser window communicate using a LocalConnection
independently from the same pages in a different browser window on the same system.