Breakout Group model

The model lies at the center of the entire applicationl it stores all the data and helps the incoming user to reach the current state of the application.

The model has only get functions and set functions. The views use the get functions to get the current state of UI Components, and the controller sets the values in the model. Every message that is passed over the network updates the Network model. The model has both Local and Network parts.

Local model

Some examples of get and set Local model functions are as follows:

• public function getMyUsername():String
• public function setMyUsername(p_name:String)
• public function getMyUserID():Number
• public function setMyUserID(p_userID:Number)

The function getMyUsername() is called by the view and setMyUsername() is called by the controller. These functions are local to the user and are called by the local controller and view and are not messaged over the network. Hence, they belong to the Local model.

Network model

The Network model involves all those functions, which are called when messages are sent over the network. Typically, for every message there is a set function call which updates the model.

Some network get and set functions for the Network model are as follows:

• public function setDiscussionTopic(p_string:String)
• public function setSelectedDisplayGroup(p_groupID:Number,p_title:String)
• public function getDisplayedGroup():Number
• public function getDiscussionTopic():String

The controller calls the setDiscussionTopic of the Local model and passes this message over the network where everyone receiving the message updates their own model by calling this function.

Similarly, when a host is displaying some group in the post view, it calls the setSelectedDisplayGroup() function on its own model and passes this message over the network. When others receive this message, they also call their setSelectedDisplayGroup() function on their Local model.

Role of the model in CaughtUp

The model plays the most important role in updating the state of the user when he enters late in the meeting. All the messages which result in calling functions on the Network model (as described above) get queued based on message type (delta/stateful—for details refer to the Adobe Collaboration Builder SDK). Every set function in the Network model is associated with a dispatchEvent, which is listened to by the view and updates itself accordingly.

The model is totally hidden from the network and the controller is the only interface of the model to the network.

Member functions of the model

As we decribed previously, member functions in the model are either get functions or set functions. Some of the functions of our Breakout Group model are as follows:

• Adding and removing groups
• Adding users to groups and removing users from groups
• Setting discussion messages
• Setting the time
• Setting text in the editor

The model has its own internal variables to perform each of these functions.

Page 3 of 9

Previous Page

Next Page