Conversation Overview
A conversation is a logical relationship automatically established and maintained by the RC SDK based on information such as the sender, recipient, and conversation type of each message. It is an abstract concept.
Conversation Types
RC supports multiple conversation types to meet various business scenarios. The client SDK uses the RCIMIWConversationType enumeration to represent different conversation types. The meanings of each enumeration value are as follows:
| Enumeration | Description |
|---|---|
| INVALID | Not supported. Reserved by the SDK. Developers cannot use this type. |
| PRIVATE | One-to-one chat |
| GROUP | Group chat |
| CHATROOM | Chatroom |
| SYSTEM | System conversation |
| ULTRA_GROUP | Ultra group chat |
One-to-One Chat
A one-to-one chat involves two users communicating directly. The two users can be friends or strangers. RC does not manage the relationship between users; the conversation relationship is established and maintained by RC.
Messages in one-to-one chat conversations are stored in the client's local database.
Group Chat
A group chat involves more than two users communicating together. 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. Each group can have a maximum of 3000 members, and there is no limit to the number of groups within the App.
Messages in group chat conversations are stored in the client's local database.
Chatroom
Chatrooms have no upper limit on the number of members, and a large number of messages are delivered instantly. Users will not receive any messages from the chatroom after they leave, and there is no push notification feature. The conversation relationship is established and maintained by RC. Users can join or leave a chatroom through the SDK's related interfaces.
The SDK does not store chatroom messages. All data in the chatroom is cleared when the user exits. For more details, please refer to the Chatroom Overview.
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 a single notification message such as a friend request.
Conversation Entity Class
The conversation entity class encapsulated in the client SDK is RCIMIWConversation. All conversation-related information is obtained from this entity class.
The following table lists the main members provided by RCIMIWConversation:
| Property Name | Type | Description |
|---|---|---|
| conversationType | RCIMIWConversationType | Gets the conversation type |
| targetId | string | Conversation ID. For one-to-one chat, it is the recipient ID; for group chat, it is the group ID; for chatroom, it is the chatroom ID; for system conversation, it is the system account ID specified by the developer |
| channelId | string | Channel ID |
| unreadCount | number | The number of unread messages in the current conversation |
| mentionedCount | number | The number of messages in this conversation where the user was mentioned |
| top | boolean | Whether this conversation is pinned |
| draft | string | Draft information saved in the conversation |
| lastMessage | RCIMIWMessage | Gets the last message |
| notificationLevel | RCIMIWPushNotificationLevel | The notification level of the conversation |
| firstUnreadMsgSendTime | number | Gets the timestamp of the first unread message in the conversation. Only effective for ultra groups |
| operationTime | number | Gets the last operation time of the conversation |