068b82b1fa
Remove parts of a previous connection monitor.
To add some context (as far as my memory goes) to the multiple connection
monitor features the product has, `stats` (currently named `connection status`)
was introduced at the Flash client back in ~2016. @fcecagno and I did it
as a BigBlueButton's Summit activity. Our work was squashed into a single
commit in 92554f8b3e :).
I'm not sure about the whole story behind `network information` (the late
connection monitor added to the HTML5 client) but I assume it should work
as a collector for a bunch of different connectivity monitors. I remember
when it was introduced but I don't know why it wasn't adopted. My best guess
would be because of some performance issues the `user list` had back then.
To follow on why `connection status` replaced `network information` at the
HTML5 client, when I did the `multiple webcams` feature I had to refactor
a big chunk of the `video provider` (#8374). Something that wasn't really
helping there was the adaptation of `stats` that was made to show local
feedback for each webcam connection. Although this feature wasn't being
used anymore, `network information` did rely on that to build up data. With
this monitor gone I assumed it was my responsibility to provide an alternative
so I promoted Mconf's port of the Flash `stats` monitor to BigBlueButton's
HTML5 client (#8579).
Well, that's my perspective on how things went for those features. If
anyone would like to correct me on something or add something else on
that history I would appreciate to know.
47 lines
1.8 KiB
JavaScript
Executable File
47 lines
1.8 KiB
JavaScript
Executable File
import '/imports/startup/server';
|
|
|
|
// 2x
|
|
import '/imports/api/meetings/server';
|
|
import '/imports/api/users/server';
|
|
import '/imports/api/annotations/server';
|
|
import '/imports/api/cursor/server';
|
|
import '/imports/api/polls/server';
|
|
import '/imports/api/captions/server';
|
|
import '/imports/api/presentations/server';
|
|
import '/imports/api/presentation-pods/server';
|
|
import '/imports/api/presentation-upload-token/server';
|
|
import '/imports/api/slides/server';
|
|
import '/imports/api/breakouts/server';
|
|
import '/imports/api/group-chat/server';
|
|
import '/imports/api/group-chat-msg/server';
|
|
import '/imports/api/screenshare/server';
|
|
import '/imports/api/users-settings/server';
|
|
import '/imports/api/voice-users/server';
|
|
import '/imports/api/whiteboard-multi-user/server';
|
|
import '/imports/api/video-streams/server';
|
|
import '/imports/api/users-infos/server';
|
|
import '/imports/api/users-persistent-data/server';
|
|
import '/imports/api/connection-status/server';
|
|
import '/imports/api/note/server';
|
|
import '/imports/api/external-videos/server';
|
|
import '/imports/api/guest-users/server';
|
|
import '/imports/api/local-settings/server';
|
|
import '/imports/api/voice-call-states/server';
|
|
import '/imports/api/auth-token-validation/server';
|
|
|
|
// Commons
|
|
import '/imports/api/log-client/server';
|
|
import '/imports/api/common/server/helpers';
|
|
import '/imports/startup/server/logger';
|
|
|
|
// Needed for Atmosphere package RocketChat/meteor-streamer
|
|
// It is out of date and was written when Meteor contained lodash
|
|
// package. However, we now import lodash as an npm package
|
|
// in order to control versions, update flexibly, etc..
|
|
// Setting the global._ to utilize the npm lodash package is an interim fix
|
|
// and its introduction was inspired by
|
|
// https://github.com/RocketChat/meteor-streamer/issues/40#issuecomment-497627893
|
|
import _ from 'lodash';
|
|
|
|
global._ = _;
|