1 person found this helpful
You may try keeping your stratus connector in a hidden frame that does not change when navigating and have it relay info to the changing "visual" applets.
This would, however, make it impossible for the hidden flash to display the peer assisted networking dialog if you intend to use netgroups. 2 possible solutions come to mind:
1. make the "invisible" frame visible at first, until you get the user to answer the peer replication dialog
2. (may not work) have the first "visible" component also connect to a group so that it triggers the replication dialog; after this is confirmed you may communicate to the "invisible" connector to also try connect to the group; since object replication is already allowed for the domain the second may connect without enquiry; or not? let us know
It's interesting solution. I'll try it tomorrow.
But would be really awesome if Adobe could create such storage in Flash Player.
Which could keep connections alive and all gathered data about group(s) as well.
It's an interesting idea and it will reduce connections made to Stratus.
Maybe some of Adobe officials will answer if there are any future plans on that feature.
Any solutions will be welcomed here as well.
Idea with frames is too complex for dynamic implementation and possibly impossible.
Any answer from adobe?
a connected RTMFP NetConnection/NetStream/NetGroup is an active construct. it's similar to a connected TCP socket. "saving" such a thing (including the UDP sockets themselves) beyond the lifetime of a running instance of Flash Player doesn't make sense and violates the web semantic.
you can do AJAXy Web2.0y stuff to change portions of a web page without loading/reloading the whole thing, which would allow you to keep an instance of Flash Player running continuously.