Conversation Overview
A conversation refers to the logical relationship automatically established and maintained by RC SDK based on the sender, receiver, and conversation type of each message. It is an abstract concept.
Conversation Types
RC supports various conversation types to meet different business scenarios. The client SDK uses the ConversationType enumeration to represent different conversation types. The meanings of each enumeration value are as follows:
| Conversation Type | Description |
|---|---|
| ConversationType.PRIVATE | One-to-one chat |
| ConversationType.GROUP | Group chat |
| ConversationType.CHATROOM | Chatroom chat |
| ConversationType.SYSTEM | System conversation |
| ConversationType.ULTRA_GROUP | Ultra group chat |
One-to-One Chat
This refers to a chat between two users, who can be either friends or strangers. RC does not maintain the relationship between users but is responsible for establishing and maintaining the conversation.
Group Chat
A group chat involves more than two users. The group member information is provided and maintained by the App, and RC is only responsible for delivering messages to all users in the group. The maximum number of members in a group is 3,000, and there is no limit to the number of groups within an App.
Chatroom Chat
A chatroom has no user limit, and massive concurrent messages are delivered instantly. Users will not receive any messages from the chatroom after they exit, and there is no push notification functionality. The conversation relationship is established and maintained by RC. Through relevant SDK interfaces, users can join or exit a chatroom.
The SDK does not save chatroom messages, and all data in the chatroom is cleared when the user exits.
System Conversation
A system conversation is established when a system account sends a message to a user. This type of conversation can be established by sending a broadcast via the broadcast interface or by sending a single notification message, such as a friend request.