This page introduces the basic concepts of Flexible Classroom, which help developers get a better and deeper understanding of Flexible Classroom.
Users are the initiator of behaviors in Flexible Classroom. A user has the following properties:
Developers can set the above user properties when calling the launch
method.
Rooms in Flexible Classroom are just like the physical classrooms in schools. Classes offered by different teachers with diversified teaching materials can take place in the same room at different times. A school can have different types of classrooms, such as traditional classrooms, laboratories, and multimedia classrooms. Similarly, the rooms of Flexible Classroom can be divided into several types. A room has the following properties:
Developers can set the above user properties when calling the launch
method. A room is created automatically with the parameters (the room ID, room name, and room type) set by the first user joining the room. To join the same room with the first user, users need to call the launch
method and pass in the same parameters (room ID, room name, and room type). Agora automatically destroys the room one hour after all users leave the room.
Classes in Flexible Classroom are just like the actual classes offered by different teachers in offline teaching scenarios. A class has the following properties:
Developers can set the above user properties when calling the launch
method. The class properties are set by the first user joining the room.
Streams in Flexible Classroom can be understood as audio and video streams and permission to send audio and video streams. Developers can call APIs to give a user permission to perform a specific operation. A user can have multiple streams. For example, a user can have both permission to send audio and video streams captured by local devices and permission to send the video stream from screen capturing.
Developers can call addCoHost
to create a stream for a user and gives the user permission to send the audio or video stream. The Flexible Classroom cloud service automatically generates a stream ID. Developers can call removeCoHost
to permanently destroy a stream and remove permission.