roomJoin not being called anymore?

[Thomas Auge]

I have an app that relies on roomJoin to track users. Somewhere between  r4572 and r4604 this stopped working. I see that r4582 "fixed" roomStop/roomStart, could that be related? Was it even intended to be used as notification for clients joining a scope below the applications scope? I.e. red5.server/chat/room123?

[Mondain]

I don't believe its our intention for that to stop working, but there have been a lot of modifications of the Scope code for the last several revisions. If it doesn't work in trunk, please post an issue report.

Paul

On Thu, Apr 18, 2013 at 8:12 AM, Thomas Auge <au...@virtues.net> wrote:

I have an app that relies on roomJoin to track users. Somewhere between  r4572 and r4604 this stopped working. I see that r4582 "fixed" roomStop/roomStart, could that be related? Was it even intended to be used as notification for clients joining a scope below the applications scope? I.e. red5.server/chat/room123?

--
 
---
You received this message because you are subscribed to the Google Groups "red5" group.
To unsubscribe from this group and stop receiving emails from it, send an email to red5interest...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
http://gregoire.org/
http://code.google.com/p/red5/

[sybersnake]

I did a lot of work in Scopes last year.  I can tell you that If you override methods and do not execute the "super" version; you will have a bad time.  It is very easy to do something in Scope/Application code that will totally break Red5's handling of that Scope.

Chances are that Red5 is working just fine but you have overridden something incorrectly.

[Thomas Auge]

Only appLeave was missing the super call - which might explain the ghost connections. :)

I'm joining people into the room from the server side using IConnection.connect(IScope scope, Object[] params).

If the scope does not exist, it is being created with IScope.createChildScope(String name). This part seems to work, because roomStart is being logged. 

The next step in my application is a roomJoin(IClient client, IScope scope) override, which worked perfectly up to 4572, but doesn't get called in 4604 anymore.

There has been some scope work in between the two. Maybe the way I'm connecting people to the new scope is flawed and should have never worked, or maybe something in red5 is broken. Dunno. :)

Only appConnect, appLeave, roomJoin, and roomLeave are overridden.

[Thomas Auge]

Here's a debug log of what's happening during the room switch ...

[Thomas Auge]

The scopes getClients() method does not show the client in the scope. So the problem isn't roomJoin not being called, but IConnection.connect() not joining the client at all.