Hi Joachim, i got it. Yes, i´m using non-persistent SO. My problem is that i need to maintain a list of all users connected in my application (users online in my cardGame lobby). Users can leave the lobby (disconnect from the mainScope) and connect in a Room (childScope). But another users connected on lobby (mainScope) need to see who are connected in the whole game(mainScopes and all childScopes). And lets suppose that all the users connnected on the lobby went to the rooms, in that case Red5 destroy my SO on the mainScope (that stores all users connected on the lobby). In that manner the next client that connects on the lobby gets an error, because the usersOnLineSO doesn´t exist anymore.
On FMS we was using proxy SO, with all rooms connected on the mainLobby (using netconnection), and maybe because this FMS don´t destroy all the SO´s on the main Lobby ! Do you have some suggest ? Thanks a lot and congratulations again for the Red5 Team ! Luiz Filipe. -----Mensagem original----- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] nome de Joachim Bauch Enviada em: domingo, 21 de janeiro de 2007 14:03 Para: [email protected] Assunto: Re: [Red5] SharedObject - Last client disconnected destroy SO Hi Luiz, Luiz Filipe schrieb: [...] > When the application starts (appStart) all the so´s are created. After that > the clients can subscribe to them without problem. > But when the last client disconnects from the main lobby (root scope where > the so´s were created), red5 > destroy all the SO´s. In that manner when another client tries to connect to > the mainLobby we don´t have > the SO´s anymore. are you using non-persistent SOs? They are supposed to be destroyed when the last client disconnects from them. 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
