Add a wildcard for getRecordings

liuzhe02 / bigbluebutton

Automatically exported from code.google.com/p/bigbluebutton

0 stars 0 forks source link

In the Moodle Integration there is a function that allows the creation of 
separated rooms in a course for each configured group. If the meeting is set to 
be recorded there should be a recording for each room generated.

The problem is for courses with a large number of users/groups. 

getRecordings is executed like this:

getRecordings?meetingID=fknai641f9831-1-1[1],fknai641f9831-1-1[2],fknai641f9831-
1-1[3]

Doing something like this would cause overload of the BBB server when there are 
many recordings:

getRecordings?meetingID=

But the query string exceeds the length allowed if there are too many groups.

One solution could be adding wildcards capability in the query like this

getRecordings?meetingID=fknai641f9831-1-1*

See: 
https://groups.google.com/forum/#!topic/bigbluebutton-users/cHu6b2KJl3Q/discussi
on

Original issue reported on code.google.com by je...@123it.ca on 28 Feb 2013 at 8:47

It's a bit of an edge case when a Moodle class had N activity links and M groups for each link, creating a URL with N * M meetingIDs. Most class have one BigBlueButtonBN activity link and no groups. To minimize changes to the BigBlueButton API, let's look at solving this first with the Moodle integration. If the integration creates a URL that is > 8kb, split it into individual getRecordings requests for each activity. Will leave this issue opened to revisit in future iterations of BigBlueButton

liuzhe02 / bigbluebutton

Add a wildcard for getRecordings #1429