Conversation Overview
A conversation refers to the logical relationship automatically established and maintained by the RC SDK based on the sender, receiver, 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 |
| ultraGroup | Ultra group chat |
One-to-One Chat
A one-to-one chat involves two users communicating directly. The users can be friends or strangers. RC does not manage user relationships but is responsible for establishing and maintaining the conversation.
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, while RC is responsible for delivering messages to all group members. The maximum number of members in a group is 3000, and there is no limit to the number of groups within an app.
Messages in group chat conversations are stored in the client's local database.
Chatroom
Chatrooms have no user limit, and massive messages are delivered instantly. Users will no longer receive any messages from the chatroom after exiting, and there is no push notification functionality. RC is responsible for establishing and maintaining the conversation connection. 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, 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 created by sending a broadcast through the broadcast interface or by sending 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 retrieved from this entity class.
The table below lists the main members provided by RCIMIWConversation:
| Property | Type | Description |
|---|---|---|
| conversationType | RCIMIWConversationType | Conversation type, as described in detail above. |
| targetId | String | Conversation ID. For one-to-one chats, it is the receiver's ID; for group chats, it is the group ID; for chatrooms, it is the chatroom ID; for system conversations, it is the system account ID specified by the developer. |
| channelId | String | Channel ID |
| unreadCount | int | Number of unread messages in the current conversation |
| mentionedCount | int | Number of messages in this conversation where the user has been mentioned (@) |
| firstUnreadMsgSendTime | int | Timestamp of the first unread message in the conversation, only effective for Ultra Groups. |
| top | bool | Whether the conversation is pinned |
| draft | String | Draft information saved in the conversation |
| notificationLevel | RCIMIWPushNotificationLevel | Do Not Disturb level |
| lastMessage | RCIMIWMessage | The content of the last message stored locally in the client for this conversation. |