Add support for HTML5 client #191
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull requests adds support for the BigBlueButton HTML5 client to GreenLight. The way GreenLight chooses which client to use is a little complex.
If a user is not authenticated then their client will be determined by what the server owner has configured. GreenLight now has a
USE_HTML5_BY_DEFAULTenvironment variable. When set to true, all unauthenticated users with join using the HTML5 client. If it is false (or not set), they will join using the Flash client.If a user is authenticated, they have the final decision in which client they use. By default, authenticated users will join using the Flash client. However, under their preferences they have the ability to toggle between the Flash and HTML5 clients.
There are three specials scenarios where the two options above are overridden.
If the HTML5 client is not running on a server, all users will be joined using the Flash client regardless of settings (and users will not have the option to toggle between clients).
If a user joins on a mobile device and the HTML5 client is running, they will always use the HTML5 client as the Flash client doesn't work on mobile devices.
If a user joins on a mobile device and the HTML5 client is not running, the user will be provided with a message stating that they are unable to join.
It also contains a few minor bugfixes introduced in BigBlueButton 2.0.