Browse Source

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

master
hristoterezov 8 years ago
parent
commit
e8223bbb4a
1 changed files with 9 additions and 2 deletions
  1. 9
    2
      modules/remotecontrol/Receiver.js

+ 9
- 2
modules/remotecontrol/Receiver.js View File

13
     REMOTE_CONTROL_MESSAGE_NAME,
13
     REMOTE_CONTROL_MESSAGE_NAME,
14
     REQUESTS
14
     REQUESTS
15
 } from '../../service/remotecontrol/Constants';
15
 } from '../../service/remotecontrol/Constants';
16
-import { getJitsiMeetTransport } from '../transport';
16
+import {
17
+    Transport,
18
+    PostMessageTransportBackend
19
+ } from '../transport';
17
 
20
 
18
 import RemoteControlParticipant from './RemoteControlParticipant';
21
 import RemoteControlParticipant from './RemoteControlParticipant';
19
 
22
 
30
  *
33
  *
31
  * @type {Transport}
34
  * @type {Transport}
32
  */
35
  */
33
-const transport = getJitsiMeetTransport();
36
+const transport = new Transport({
37
+    backend: new PostMessageTransportBackend({
38
+        postisOptions: { scope: 'jitsi-remote-control' }
39
+    })
40
+});
34
 
41
 
35
 /**
42
 /**
36
  * This class represents the receiver party for a remote controller session.
43
  * This class represents the receiver party for a remote controller session.

Loading…
Cancel
Save