I saw this from a while back.
Wouldn't it be easier to just do this?
// invoke a method on all connections to a given scope
ServiceUtils.invokeOnAllConnections( "someClientSideMethod", new Object[]{
someParameter } );
-Mike
ericfunk wrote:
>
> good idea - thanks a lot !
> i maintain a lookup map for user objects in my application as well and i
> can just add the connection to each user object.
> cheers
> eric
>
>
>
> Rob Schoenaker wrote:
>>
>>>as far as i understand this will give me the connection of the current
>>>user...
>>
>> That's what it does, yes
>>
>>>I am interested in the connection of another user
>>>Ideally something like Red5.getConnections(String clientId);
>>
>> What I do in our server is maintain a list of specific connections I
>> with for these kind of functionality. I add items on appConnect and
>> remove them on appDisconnect. Then, I can iterate the maintained list
>> and invoke the method I need.
>>
>> This prevents from excessive iterating through the internal Red5 lists.
>>
>> HTH,
>>
>> /Rob
>>
>> _______________________________________________
>> Red5 mailing list
>> [email protected]
>> http://osflash.org/mailman/listinfo/red5_osflash.org
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/calling-client-side-methods-using-service.invoke%28%29-for-a-single-user---is-there-a-better-way-than-iteration-through-a-client-list-of-the-room-....-tf4256490.html#a12443920
Sent from the Red5 - English mailing list archive at Nabble.com.
_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org
