001ab9554c
Video streams can be sorted by voice floor activity in the client according to FreeSWITCH´s floor events. The feature works together with pagination, essentially giving an Last-N like experience while not disrupting too much Made video stream sorting extensible in a way. The sorting modes for pagination and unbounded can be configured in settings.yml and new sorting modes can be added to the stream sorting util under video-provider. Inline docs explain how to do that Changed how the stream ID attribute from video-streams collection was passed to downstream components; we had an array map that was executed every change just to map stream to cameraId, which is bizarre. So I changed the cameraId usage in downstream components to be conformat with the collection attributes and shaved off the map where it wasnt needed Add better selectors to video-list-item container´s VoiceUser fetch
33 lines
832 B
JavaScript
33 lines
832 B
JavaScript
import Logger from '/imports/startup/server/logger';
|
|
import VideoStreams from '/imports/api/video-streams';
|
|
import { check } from 'meteor/check';
|
|
|
|
export default function floorChanged(meetingId, userId, floor, lastFloorTime) {
|
|
check(meetingId, String);
|
|
check(userId, String);
|
|
check(floor, Boolean);
|
|
check(lastFloorTime, String);
|
|
|
|
const selector = {
|
|
meetingId,
|
|
userId,
|
|
}
|
|
|
|
const modifier = {
|
|
$set: {
|
|
floor,
|
|
lastFloorTime: floor ? lastFloorTime : undefined,
|
|
},
|
|
};
|
|
|
|
try {
|
|
const numberAffected = VideoStreams.update(selector, modifier);
|
|
|
|
if (numberAffected) {
|
|
Logger.info(`Updated user streams floor times userId=${userId} floor=${floor} lastFloorTime=${lastFloorTime}`);
|
|
}
|
|
} catch (error) {
|
|
return Logger.error(`Error updating stream floor status: ${error}`);
|
|
}
|
|
}
|