Problems for bigbluebutton_rails when meetings are created from another system

[mconf-daileon]

---

Author Name: Leonardo Daronco (Leonardo Daronco) Original Redmine Issue: 153, http://dev.mconf.org/redmine/issues/153

---

@Google user: [email protected]@

This ticket was created to keep track of potencial problems for bigbluebutton_rails when another system is also used to create/manage BBB meetings.

When the list of meetings is fetched from a BBB server, any meeting that is not yet in the database will be created and saved. If the room is already in the DB, its attributes will be updated. See "https://github.com/mconf/bigbluebutton_rails/commit/02b472f82bbe52f2d753c67a55341268de374395" rel="nofollow":https://github.com/mconf/bigbluebutton_rails/commit/02b472f82bbe52f2d753c67a55341268de374395

If the meeting was not in the DB it means that it was created from another application (BBB demos, Android client, etc). This raises two issues:

• Since we didn't create the meeting, we don't have all the parameters passed in the creation. Unfortunately there are some parameters you can't access through the API after creating a meeting. So there will probably be inconsistencies in these parameters between the meeting in the DB and the meeting running in the server. These parameters are:
  • welcome (the welcome message)
  • voiceBridge
  • logoutURL
  • maxParticipants
• Adding or updating this meeting in the DB might result in conflicts with already existent meetings.

[mconf-daileon]

---

Original Redmine Comment Author Name: Leonardo Daronco (Leonardo Daronco) Original Date: 2011-07-17T03:00:00Z

---

@Google user: [email protected]@

We don't automatically save the fetched meetings in the DB anymore (see "/p/mconf/issues/detail?id=176": Issue 176 ), so the problem is partially solved.

The application using the gem will have to decide if the meetings should be saved or not and then deal with the possible errors.