1 person found this helpful
You could build your own listener/dispatcher system in a single control swf and give all the other swfs a common localConnection name to register their own individual localConnection names with.
After one of the child swfs updates, it notifies the control swf which notifies all other child swfs.
I realize this is simply stream-lining your local connection idea, but this would be flexible and scalable.
My only other thought would be to use a non-swf native app.
Yea, I thought about that also, kind of creating a stack, however there are 2 main issues with that. A timer is still implemented for the 'controlling SO' swf to check for updates, and when / where does the main SWF get created. Let's say the user has a SWF off my home page www.myexampleurl.com, one a subsequent page: www.myexampleurl.com/checkScores.php, and one in a MySpace widget (LOL myspace) www.myspace.com/myspaceIsLame then the main homepage would create this SWF, however if the user doesn't have the homepage open, where would the SWF go? This would require working out each application to determine if it has premissions to open up it's own instance of this swf to handle things.
To do it right, seems like it would take a long time, and to do it fast, seems like it would get super sloppy super fast. I do appreciate your help though!
Any other thoughts?
I'm not sure you would need a timer if you relied on each individual child swf to actively communicate changes with the controller.
It does complicate things not knowing which page is pulled up first or if that page is closed. Is opening the control swf in a new window an option?
If so, you could have each child check for the control swf and open a new window if it can't be found. This would be a fragile solution though.