Consider storing all fetched attributes in the DB

[mconf-daileon]

---

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

---

@Google user: [email protected]@

Consider if all the information fetched from a BBB server should be saved in the DB or not. Some of this information is stored only in instance variables in the models, so they are lost between requests. Saving them is the only way to fully compare models between two requests.

• For rooms the attributes are: running, participant_count, moderator_count, attendees, has_been_forcibly_ended, start_time, end_time.
• Servers have only the attribute "meetings", but it is already saved as BigbluebuttonRoom's models.

There are some complications in saving "attendees", since they are objects with their own attributes. It would require another table for attendees and the setting up of the relationship between attendees and rooms.