haskal
/
jiti-meet
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix(remotecontrol): Use own scope for the messages. (#1787)

This commit is contained in:
hristoterezov 2017-07-25 10:40:57 -05:00 committed by virtuacoplenny
parent fa86d2ab9e
commit e8223bbb4a
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
modules/remotecontrol/Receiver.js
View File

@ -13,7 +13,10 @@ import {
REMOTE_CONTROL_MESSAGE_NAME, REMOTE_CONTROL_MESSAGE_NAME,
REQUESTS REQUESTS
} from '../../service/remotecontrol/Constants'; } from '../../service/remotecontrol/Constants';
import { getJitsiMeetTransport } from '../transport'; import {
Transport,
PostMessageTransportBackend
} from '../transport';
import RemoteControlParticipant from './RemoteControlParticipant'; import RemoteControlParticipant from './RemoteControlParticipant';
@ -30,7 +33,11 @@ const logger = getLogger(__filename);
* *
* @type {Transport} * @type {Transport}
*/ */
const transport = getJitsiMeetTransport(); const transport = new Transport({
backend: new PostMessageTransportBackend({
postisOptions: { scope: 'jitsi-remote-control' }
})
});
/** /**
* This class represents the receiver party for a remote controller session. * This class represents the receiver party for a remote controller session.