True. I meant connection.connect instead of join. Like here: http://cosmincimpoi.blogspot.com/2007/08/re-red5-how-to-move-new-client-to.html I really don't feel join is any good anyways. But as I said I have yet to be corrected by anyone who walks the path :)
cosmin > Thank you for your response. i don't know what do you mean with : > > "Or from appConnect using connection.join(scope)" > > IConnection haven´t this method. > > Thanks a lot again. > > > > [EMAIL PROTECTED] escribió: >> After some days of trying same thing I settled for client side scope >> change. >> My current belief is that scopes can be succesfully changed only from >> client. Or from appConnect using connection.join(scope). >> >> If someone else asks again about this I ll post some really dumb and >> impossible answer so one of the devs will feel the urge to clarify this >> matter for all of us. >> >> cheers, >> cosmin >> >> >>> Hi, i have a doubt with mehtod 'public boolean *join*(IClient >>> <http://dl.fancycode.com/red5/api/org/red5/server/api/IClient.html> >>> client, >>> IScope >>> <http://dl.fancycode.com/red5/api/org/red5/server/api/IScope.html> >>> scope)' >>> of class ApplicationAdapter. I would like to manage user's room on >>> server-side in the application i'm developing. >>> I have a method on server-side named 'boolean joinToRoom (Object[] >>> params )' that I invoke from clien-side. The code of this method is: >>> >>> boolean joinToRoom (Object[] params ) { >>> >>> String roomDestinyName = (String) param[0]; //Name of >>> destiny room >>> ... >>> IConnection connOrigin = Red5.getConnectionLocal(); >>> >>> IScope roomDestiny = >>> this.getScope().getScope(roomDestinyName ); //Get destiny room >>> >>> boolean res = this.*join*(connOrigin .getClient(), >>> roomDestiny ); //Join the current user to the requested room >>> .... >>> } >>> >>> But this method doesn't work. The current user stay in the original >>> room. >>> The source code for this methos is: >>> >>> public boolean join(IClient client, IScope scope) { >>> if (!super.join(client, scope)) { >>> return false; >>> } >>> if (isApp(scope)) { >>> return appJoin(client, scope); >>> } else { >>> return isRoom(scope) && roomJoin(client, scope); >>> } >>> } >>> ¿Where is the lodic to manage rooms? >>> The description in the API says: >>> "Adds client to scope. Scope can be both application or room. Can be >>> applied to both application scope and scopes of lower level." >>> >>> Am I on the wrong way?? What does this method do really? >>> >>> I don't want to use the 'URL alternative' to manage rooms: >>> "rtmp://host/app/room1/room2" >>> >>> Thanks lot. >>> >>> >>> -- >>> *Caymasa El Sendero* *Angel Peña Ruiz Departamento de Desarrollo* >>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >>> --http://www.elsendero.es-- >>> tel.: 95 448 64 11 / fax: 95 448 48 03 >>> >>> >>> _______________________________________________ >>> Red5 mailing list >>> Red5@osflash.org >>> http://osflash.org/mailman/listinfo/red5_osflash.org >>> >>> >> >> >> _______________________________________________ >> Red5 mailing list >> Red5@osflash.org >> http://osflash.org/mailman/listinfo/red5_osflash.org >> >> >> > > > -- > *Caymasa El Sendero* *Angel Peña Ruiz Departamento de Desarrollo* > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > --http://www.elsendero.es-- > tel.: 95 448 64 11 / fax: 95 448 48 03 > > > _______________________________________________ > Red5 mailing list > Red5@osflash.org > http://osflash.org/mailman/listinfo/red5_osflash.org > _______________________________________________ Red5 mailing list Red5@osflash.org http://osflash.org/mailman/listinfo/red5_osflash.org
