fix(remotecontrol): Use own scope for the messages. (#1787)
This commit is contained in:
parent
fa86d2ab9e
commit
e8223bbb4a
|
@ -13,7 +13,10 @@ import {
|
|||
REMOTE_CONTROL_MESSAGE_NAME,
|
||||
REQUESTS
|
||||
} from '../../service/remotecontrol/Constants';
|
||||
import { getJitsiMeetTransport } from '../transport';
|
||||
import {
|
||||
Transport,
|
||||
PostMessageTransportBackend
|
||||
} from '../transport';
|
||||
|
||||
import RemoteControlParticipant from './RemoteControlParticipant';
|
||||
|
||||
|
@ -30,7 +33,11 @@ const logger = getLogger(__filename);
|
|||
*
|
||||
* @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.
|
||||
|
|
Loading…
Reference in New Issue