Hi Joachim,
>> Well, I hope this helps in understanding the concept of scopes in
Red5. <<
Superb. It really works.
But I have maybe found a bug.
I am using so.setAttribute to spread info about connected people to room.
To get clients in scope I am using this method:
private ArrayList<String> getClientNames(IScope scope){
Iterator<IClient> it = scope.getClients().iterator();
ArrayList<String> clientNames = new ArrayList<String>();
while (it.hasNext()) {
IClient client = it.next();
// get my special "nick" attribute, which I set to user in event in
appConnect - should this be a problem?
clientNames.add(client.getAttribute("nick").toString());
}
return clientNames;
}
But even when clients disconnects - the users are still in room.
That means ... I connect 5 clients ... and disconnect.
The sixth client will get in SO, that there are 6 clients connected to room
(using my method getClientNames) (but they are not).
And that's quite interesting. They should be deleted automatically.
I call getClientNames(room) in roomJoin.
Thanks
Tom Krcha
FOA: As already said, I am using trunk version.
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
