If I do a server side connection.connect( newScope ) I get the following
problems:
- client shared objects do not resync
- setting a shared object property from the client works
- calling a method on the server from the client fails with [Error
executing call: Service: null]

In most of my server side callable methods I use
Red5.getConnectionLocal(). Is there another way to get the conn reference?
Note that on scope change all the handlers ( roomStart, appConnect,
roomConnect, roomJoin ) are triggered correctly. This however does not
reflect at all on the client side.

So dear red5 core devs, does scope change really work only from explicit
client connect to app/room urls in Red5 or NOT?

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

Reply via email to