ApsaraMQ for RocketMQ provides HTTP client SDKs for multiple programming languages. You can use the SDKs to access ApsaraMQ for RocketMQ over the Internet. This topic describes the release notes for HTTP client SDKs for multiple programming languages.
SDKs written in different programming languages
- Make sure that the resources that you want to access is in the same region as the HTTP endpoint.
For example, if your ApsaraMQ for RocketMQ instance is deployed in the China (Hangzhou) region, you can access the instance only by using an endpoint of the China (Hangzhou) region. You can access the instance in the following scenarios:
- If your client is located in the China (Hangzhou) region, we recommend that you access the instance by using the internal HTTP endpoint of the instance.
- If your client is not located in the China (Hangzhou) region, make sure that your client can connect to the Internet and can access the instance by using the public HTTP endpoint of the instance.
- Messages can be transmitted between TCP and HTTP clients. The message information such as attributes, content, tags, and keys must comply with XML rules because HTTP uses XML serialization.
If messages contain characters that do not comply with XML rules, the following errors may occur:
- Messages fail to be sent over HTTP.
- Messages fail to be consumed over HTTP when messages are sent over TCP.
You can use Base64 to encode or decode messages that do not comply with XML rules.