Problem

While in a room, occupants have different communication needs and privileges. A "speaker" in a meeting application might have the ability to send messages to all other users in the room, while an "attendee" might not. Application development would be easier if the concept of communication needs and privileges were built into the development API.

Solution

Implement different client roles for room occupants, on a per-room basis. Each client's role determines its communication profile and permissions.

Some built-in:

• Spectator
• Moderator

Some custom:

• Speaker
• TeamA/TeamB

Implementation

• Users specify role(s) at room join time
• Available room roles are specified at room-creation time
• Send message UPCs can filter by roles
• Roles might determine synchronization policy