Thanks for the guidance. I've left my SO creation in the appStart and moved the getSharedObject to the appConnect and it seems to work as we wanted. That is, after all connections are dropped to the application, the next app to connect reconnects to the SO (or creates a new one). I have a feeling that the the old SO is still there because the new connect app sees the old values of some of the parts.
Anyway, problem appears to be solved. Bill Joachim Bauch wrote: > Interalab schrieb: >> I suppose that if you attempt to create an SO, it will just connect >> to it if it exists. So, I could just attempt to create it on every >> appConnect. Do you think there's a problem with that? Will creating >> it destroy any data already contained in it? > > yes, creating a SO means creating a new one. But you can use > so = getSharedObject(scope, name, persistent) in your appConnect > instead. This method returns the shared object with the given name > or creates a new one if it doesn't exist. > > Joachim > > ------------------------------------------------------------------------ > > _______________________________________________ > Red5 mailing list > [email protected] > http://osflash.org/mailman/listinfo/red5_osflash.org > _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
