Increase response timeout while testing URL #90
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
The normal timeout might be sufficient for a BBB-server with zero or only a few meetings. But for example a scalelite-server, having hundreds of meetings at the time of testing, does respond not fast enough. An increasing of the timeout solves the problem.
|
@agru HOW to fix this? How to go about "increasing the timeout"? |
|
@jfederico - any chance you could accept and merge this PR - it is a super simple fix with no side effects. For some use cases the plugin is almost unusable with such a low timeout. Thanks! |
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.
The normal timeout might be sufficient for a BBB-server with zero or only a few meetings. But for example a scalelite-server, having hundreds of meetings at the time of testing, does respond not fast enough. An increasing of the timeout solves the problem.
Reason for this change was, that I already had problems in saving the default settings with the server http://test-install.blindsidenetworks.com/bigbluebutton/. After increasing the timeout everything worked fine. And now I was also able to change to our own scalelite that had hundreds of active meetings at that time.