Thanks, So what you propose to do?
Because I thought that appConnect is the method for rejecting client. And that appJoin is that he was already approved and he is in the room. Would be good to have there something like "appAlreadyJoined" and appAlreadyLeft Thanks Tom -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joachim Bauch Sent: Thursday, September 28, 2006 4:53 PM To: [email protected] Subject: Re: [Red5] appJoin appLeave - logical problem Hi Tom, Tom Krcha wrote: > When user connects the appJoin is executed. And I need to let other > connected clients know that there is someone new by setting shared object. > > But this time (appJoin) the scope.getClients() is empty. > > So the problem is, that maybe you add client to scope after appJoin, but > the user must be there before it. No? No, the method is called when the user is about to enter the room, i.e. he isn't in it yet. It's called before the user entered, so he can be rejected before he is in the room. > The same situation is at appLeave. When I write connected clients > (scope.getClients()), the user is still there, but he already left the > room, no? Same here, the user is about to leave the room, i.e. has not yet left. Joachim _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
