Add Low-Priority Message Types
To ensure the delivery of important messages in chatrooms, the chatroom service may discard the latest messages that exceed the consumption limit in chronological order when the message volume is large, ensuring server stability.
Apps can use the Chatroom Low-Priority Message feature provided by the chatroom service to configure up to 20 message types as low-priority message types. When the server is under high load, if low-priority messages are received, they will be discarded first. For example, if an App has custom like messages, they can be configured as low-priority message types and discarded first when the chatroom message volume is high.
- By default, all messages are high-priority messages. The server's default processing capacity for incoming messages in a single chatroom is 40 messages per 200 milliseconds. Among these, 20 messages are reserved for high-priority messages, and the remaining 20 messages are shared between high-priority and low-priority messages. After configuring low-priority message types, the server will process high-priority and low-priority messages based on the above quotas under high load conditions, with low-priority messages being discarded first to free up the shared quota for high-priority messages.
- A single chatroom supports configuring up to 20 message types as low-priority message types. By default, all messages are high-priority messages.
The Chatroom Low-Priority Message feature is used to prioritize discarding certain messages. If you need to protect important messages, please use the Chatroom allowlist and Chatroom Message allowlist features. For more details, see Chatroom allowlist Service Overview.
Enable the Service
Before using the Chatroom Low-Priority Message feature, please ensure that the service has been enabled for the current App Key.
If the service is not enabled, the Server API will return a 1009 error. Note that if the service is not enabled and continuous requests cause the API request frequency to exceed the limit, the Server API will return an HTTP 429 Too Many Requests error (error code 1008).
Request Method
POST: https://Data Center Domain/chatroom/message/priority/add.json
Rate Limit: 100 requests per second
Signature Rule: All server API requests require rule verification. For details, see API Request Signature.
Body Parameters
The HTTP request body data format is application/x-www-form-urlencoded, and the following HTTP form parameters are supported:
| Parameter | Type | Required | Description |
|---|---|---|---|
| objectName | String | Yes | The low-priority message type. You can submit up to 5 types at a time, with a maximum of 20 types. |
Request Example
POST /chatroom/message/priority/add.json HTTP/1.1
Host: api.rong-api.com
App-Key: uwd1c0sxdlx2
Timestamp: 1408710653491
Nonce: 14314
Signature: 45beb7cc7307889a8e711219a47b7cf6a5b000e8
Content-Type: application/x-www-form-urlencoded
objectName=RC:VcMsg&objectName=RC:ImgTextMsg&objectName=RC:ImgMsg
Response
The HTTP response body contains a JSON object with the following structure:
| Return Value | Return Type | Description |
|---|---|---|
| code | Number | Return code, 200 for success. |
Response Example
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
{"code":200}