BigBlueButton 0.81 accepts a config.xml file on create calls (see https://code.google.com/p/bigbluebutton/issues/detail?id=294). This file is used to configure a lot of things in the meeting, overriding pre-configured options in the server.
@bigbluebutton-api-ruby@ should also allow this filed to be passed on @create@ calls.
It should receive either a full config.xml file or a new object (some new class like @BigBlueButton::BigBlueButtonConfigXML@, as is done to pass a presentation for pre-upload) that has all available parameters that can be set in a config.xml and that will create a config.xml dynamically.
Author Name: Leonardo Daronco (Leonardo Daronco) Original Redmine Issue: 961, http://dev.mconf.org/redmine/issues/961
Original Assignee: Leonardo Daronco
BigBlueButton 0.81 accepts a config.xml file on create calls (see https://code.google.com/p/bigbluebutton/issues/detail?id=294). This file is used to configure a lot of things in the meeting, overriding pre-configured options in the server.
@bigbluebutton-api-ruby@ should also allow this filed to be passed on @create@ calls. It should receive either a full config.xml file or a new object (some new class like @BigBlueButton::BigBlueButtonConfigXML@, as is done to pass a presentation for pre-upload) that has all available parameters that can be set in a config.xml and that will create a config.xml dynamically.