[jitsi-users] JitsiConference sendCommand vs sendCommandOnce


#1

Can someone explain the difference between "sendCommand / removeCommand"
and "SendCommandOnce"?

I have seen that in jitsi-meet a command is sent with sendCommand
(avatar-id) and then that command is triggered whenever there is an event
or new command in the room.

Thanks !


#2

I would suggest to avoid using this API and use participant properties instead. You can set a property for the local participant with
JitsiConference.setLocalParticipantProperty(name, value), and you can
detect changes to properties for remote participants by listening for
JitsiConferenceEvents.PARTICIPANT_PROPERTY_CHANGED events from the JitsiConference.

Boris

···

On 16/12/2016 03:19, Germán Figna wrote:

Can someone explain the difference between "sendCommand / removeCommand"
and "SendCommandOnce"?

I have seen that in jitsi-meet a command is sent with sendCommand
(avatar-id) and then that command is triggered whenever there is an
event or new command in the room.


#3

Thanks Boris !

···

2016-12-16 16:16 GMT+01:00 Boris Grozev <boris@jitsi.org>:

On 16/12/2016 03:19, Germán Figna wrote:

Can someone explain the difference between "sendCommand / removeCommand"
and "SendCommandOnce"?

I have seen that in jitsi-meet a command is sent with sendCommand
(avatar-id) and then that command is triggered whenever there is an
event or new command in the room.

I would suggest to avoid using this API and use participant properties
instead. You can set a property for the local participant with
JitsiConference.setLocalParticipantProperty(name, value), and you can
detect changes to properties for remote participants by listening for
JitsiConferenceEvents.PARTICIPANT_PROPERTY_CHANGED events from the
JitsiConference.

Boris

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users