Hi,
   I'm trying to learn the Red5 API and int the process, I started creating
a chat application. I have a separate class which helps me to manage all the
rooms (sub scopes) available in the the main  lobby (the parent scope
variable in application adapter ). When a user tries to join one of the
rooms, I have a manual function on the server called JoinRoom( String
RoomName ) which I call from the client in order to let them join the room.
In this function, I use scope.getScope(RoomName) to check if the room
already exist, if not, I create it with addChildScope and then manually
connect the client to this scope by using scope.getScope(RoomName).Connect(
Red5.getConnectionLocal() ). I did this because I want to recycle the
netconnection used by the client in the first time (when connecting to the
parent scope), instead of creating a new netconnection to the chilld room.

However I find that each time I call scope.Connect, it actually initiates a
whole new IConnection to the application altogether ( it calls appstart
again instead of just roomJoin ). I'm wondering what is the intended
behaviour because this seems quite strange to me. Does anyone have a
suggestion on how I should go about implementing this? it'll be greatly
appreciated.

Another issues is that when I manually create a scope with the
createChildScope() function, it does not seem to destroy the sub-scope even
after all connections have left it. Do I have to manually destroy it or will
it destroy itself after a while?

Thanks in advance
Jerry
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org

Reply via email to